Mcgillivray, Don [ITS]
donald.a.Mcgillivray at mail.sprint.com
Wed Jun 1 10:54:24 CDT 2005
And (acknowledging that you may have simply banged out a simple SQL statement for illustrative purposes) "CurrentDB.Execute" works only for "action" (update, append, delete, etc.) queries. A select query won't "execute". Don -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Wednesday, June 01, 2005 8:10 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Queries vs In-line SQL In 2000 and later, saved queries are optimized and so should execute faster than on the fly queries, including the sort generated in code. Charlotte Foust -----Original Message----- From: Joe Rojas [mailto:JRojas at tnco-inc.com] Sent: Wednesday, June 01, 2005 6:32 AM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Queries vs In-line SQL Is there a performance increase between in-line SQL and queries in Access 2000? For example: Going from CurrentDB.Execute "SELECT * FROM MyTable" To putting the SELECT statement above in a query? Thanks! JR