Mark Breen
marklbreen at gmail.com
Tue May 14 02:49:06 CDT 2013
Hello Stephen, this only way I build my ODBC connections it from within Access. I think I usually use machine DSN. I simply click the builder in the connection string section of the pst and choose or create a ODBC from within Access. If I create it for the linked tables, I can simply select it from the pst, or vice versa but I always seem to have to create the odbc from within access. This method works well for me for years. Mark On 14 May 2013 05:40, Stephen Bond <stephen at bondsoftware.co.nz> wrote: > CROSS POSTED > > Neophyte question ... > > Windows 7. Access 2010. SQL Server2008R2. > > In my ODBC Data Source I have set up a UserDSN and a SystemDSN, pointing > to the SQL back-end I'm reporting from (copy of customer's SQL back-end, > on my PC). > > When I send the Access 2010 front end to the customer to test, the > LinkedTable Manager re-links to the SQL tables OK but the > PassThroughQueries fail. I checked the PassThroughQuery Properties, and > the ODBC Connect String includes "ODBC;DSN=myName; ..." etc. The PTQ is > coughing at the lack of resolution of 'myName'. > > I checked at the customer site and they don't have any UserDSN or > SystemDSN set. They are relying on a DSN file. When they use the > LinkedTable manager it strips my 'DSN=' from the table re-connection ... > how do I cope with the same on PassThrough Queries? > > > Stephen Bond > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > >