Jim Lawrence
accessd at shaw.ca
Fri May 22 00:00:47 CDT 2009
Hi John: I have been working with MS Access to ADO-OLE to MS SQL/Oracle DBs since 1997 and Access does not work with ODBC. There is a simple and stupid way to up date an old Access MDB to a MS SQL BE using connection/links. This system actually works fine for delete, add and update... but as soon as you start grabbing recordsets of data for reports, subforms or start rolling out a new application to a remote desktops the whole system grinds to a halt. At that point you have reached the end of the usefulness of the ODBC connections. Unfortunately there is no short cut, the client and you just have to bite the bullet and go straight ADO-OLE... It is not that difficult but the nice gui interface within Access can not do it. Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Thursday, May 21, 2009 3:48 PM To: Access Developers discussion and problem solving Subject: [AccessD] Linked to SQL Server in a domain Guys, I am a tad out of my comfort zone here. I am working on a database that links to a SQL Server using ODBC. The database was "upgraded" by another company which is in the process of being fired. The links work but I do not know where the DSN file resides. I created a new database and a DSN for new tables that I created in that database and it works just fine for me, logged on to the server (which is where I work - remote desktop), but it does not work for another user that I have helping me test. Those new links to the new table gives an ODBC error when she just tries to open the tables directly in the table tab of the db window. I am assuming that is because the DSN file I used to do the link is not on her computer? Is that the way this works? How do I discover where the DSN file is for the database that existed already when I first got in? I tried looking at the TDF cnn data and it isn't referenced in there. I found this: http://support.microsoft.com/kb/892490 Which looks like the magic key. Does anyone use this code or something similar? Any comments, warnings? Unfortunately at this point I am not able to log in to any other workstation there to test this code from another workstation. I will have to get that figured out as well. Any help appreciated. -- John W. Colby www.ColbyConsulting.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com