Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
osupratt
Posting Yak Master
238 Posts |
 Posted - 2008-03-13 : 11:59:10
|
| I have a database that sits on my network. There are linked tables (read and write) from FE - Access to BE - SQL Server. When logging in or out of this database I used to get an 'ODBC connection fail' until I added code for DSN-less connection.Now I went to the End-user who is also on the network and is using the same database, but they are getting the 'ODBC connection fail' again. The code is on their database too. I don't understand what is going on.Do I need to re-create all the linking on the end-user's computers or what? If anyone has done this before or knows what to do you'd definately be a life saver. Thank you. |
|
|
jsmith8858
Dr. Cross Join
7423 Posts |
Posted - 2008-03-13 : 12:32:56
|
| Are you using a sql login, or windows authentication? If it is sql authentication, did you save the username/password when linking? And if it is windows, are you sure the end user has correct permissions?Also, review the connect string to be sure it is set up the way you want. you should create a "FILE DSN", which ends up embedding all the ODBC info you need in the connect string. To review a connect string for a linked table, you need to :1) go to design view on the linked table (ignore the warning)2) Select View->Properties from the main menu.the connect string property is displayed first, so review that to ensure it has what you need.- Jeffhttp://weblogs.sqlteam.com/JeffS |
 |
|
|
|
|
|
relink tables FE to BE - HELP!