Query Efficency and Best Practice

[psycoperl]

I am looking for both Best Practice and Best Efficency for doing a calculation

Is it faster to do simple calculations on two fields in SQL while running my query or in VBA after the query.

 

[Joe4]

It probably really depends on exactly what you are trying to do, but if it really is a simple calculation that can be done in your query, then I think there should be no reason to involve VBA. VBA is a great tool, but no need to unnecessarily complicate matters when a simple solution will do.

 

[HiTechCoach]

If performace is critical then I keep teh query as simple as possible. No caclulations.

I perform the calculatson at the form or report level. A lot of time this can be done in a control's control source without any VBA code.

PS:
"Give a man a fish, feed him for a day. Teach a man to fish, and he will sit in a boat a drink beer all day!"

 

[Joe4]

"Give a man a fish, feed him for a day. Teach a man to fish, and he will sit in a boat a drink beer all day!"

You say that like there's something wrong with that!
Actually, I am a fisherman, but am usually all business when I fish, which means no beer to slow me down. The beer usually comes when eating the fish dinner!

 

[psycoperl]

If performace is critical then I keep teh query as simple as possible. No caclulations.

I perform the calculatson at the form or report level. A lot of time this can be done in a control's control source without any VBA code.

PS:
"Give a man a fish, feed him for a day. Teach a man to fish, and he will sit in a boat a drink beer all day!"

You say that like there's something wrong with that!
Actually, I am a fisherman, but am usually all business when I fish, which means no beer to slow me down. The beer usually comes when eating the fish dinner!

Thanks all... even for the fishing talk ... reminds me it has been too long since I went fishing.

 

[HiTechCoach]

You say that like there's something wrong with that!

Naw ... its da Redneck way.