Jim Dettman
jimdettman at verizon.net
Fri Apr 26 08:14:29 CDT 2013
<<First of all I need to know whether that is faster, slower or no difference.>> Slower. << Is it possible to use this kind of thing using an ODBC connect string? Or does an ODBC connect string assume a database server / engine at the other end?>> Yes. The syntax allows for any database type that JET can ordinarily connect to (FP, ODBC, dbase, Paradox, etc). Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John W Colby Sent: Friday, April 26, 2013 08:41 AM To: Access Developers discussion and problem solving Subject: [AccessD] Querying the back end directly I know that queries can be constructed to use a "SELECT FROM ExternalFileName.Table" kind of syntax. In other words, not linking a table out in the BE but in the query referencing the external database (or spreadsheet etc) and then a table inside of that. First of all I need to know whether that is faster, slower or no difference. I need to be able to modify that to modify the location of the back end file. While I can open the query def and search through the sql for the file name I would really prefer not to. Is it possible to use this kind of thing using an ODBC connect string? Or does an ODBC connect string assume a database server / engine at the other end? -- John W. Colby Reality is what refuses to go away when you do not believe in it -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com