Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Record Source as a Query or Sql?

Status
Not open for further replies.

PCX

Technical User
Dec 17, 2000
54
US
I have a report that uses 20+ queries to get the desired reports. Each time the report runs I use code to assign a different query as the record source and print the report.

I found I could also use embedded SQL statements in the code and branch with IF-Then statements to accomplish the same thing.

My question is... which is better? Is there one way that is more efficient or faster? They both seem to run with similar results and speed so far. But as the program expands will I see a slow down using one over the other?

Maybe there is another way to change the query criteria and/or query tables on the fly to reduce the number of queries used?

Thanks
 
Saved Queries when run once have been optimized by ACCESS to run with the most effecient manner and speed. SQL srings are not optimized and with large data files will run slower. But, if you data files are not signficantly large you probably will not see a difference.

You might want to read up on Query Optimization in ACCESS Help to better understand this process.

Bob Scriver
[blue]Want the best answers? See FAQ181-2886[/blue]


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top