If you are using access as your backend, your bottleneck is most likely going to be it's inability to handle a high number of concurrent requests, not the speed of a single query. The best thing you can do to improve speed would bo to upgrade to SQL Server, MySQL, or some other database solution that supports more concurrent sessions.
Spending alot of time worrying about prebuilt vs inline queries in Access will be mis-spent time. -Cameron On Mon, 27 Dec 2004 14:18:22 -0400, Ron G <[EMAIL PROTECTED]> wrote: > I am tryin to determine which is more efficient: embedded sql statement or > querying a saved query on the database end. I am using access. I have tried > it on a simple query where I select all records from one table where the > date = yesterday. I ran it both ways and my tick count was half when I query > the prebuilt query than when I use imbedded sql. > > However a co-worker told me he has heard that using pre-built queries rather > than imbedded sql has its drawbacks but doesn't remember what the reasoning > was. > > I would really appreciate any comments anyone has on this topic. > > Thanks > > Ron > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Silver Sponsor - RUWebby http://www.ruwebby.com Message: http://www.houseoffusion.com/lists.cfm/link=i:4:188845 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
