Link to home
Start Free TrialLog in
Avatar of kshumway
kshumwayFlag for United States of America

asked on

DSN Connection

I've inherited an access database that has a SQL Server back end.  When looking at the Linked Table Manager, it shows, after the table name, (DSN = LAAT; Database = LAAT).  The table data is available even though there is no LAAT datasource on the workstation.

Today we copied the tables for the LAAT to a new SQL Server.  However, no matter what I've tried, I cannot view the data in the new database unless I add a datasource connection to the workstation  We have users across the company in multiple locations, and setting up the ODBC datasource on each workstation would be time consuming which I assume is why this type of connection was selected initially.  Does anyone know how I can view the new table's data without visiting every workstaton to set up a new datasorce?
Linked-Table-Manager.doc
ASKER CERTIFIED SOLUTION
Avatar of Scott McDaniel (EE MVE )
Scott McDaniel (EE MVE )
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of kshumway

ASKER

Thank you.  I am looking at the DNSLessLink article.
I have been playing with this by creating two small database (one table each) on each of the servers.  KSQLDB is the server where the database currently resides.  KSQL is the new server.  I am getting the following error on the line
dbCurrent.Tabledefs.Append tdfCurrent:

ODBC - connection to '(sql server)KSQL' failed. (3151) encountered.

My connection string is:

ODBC:DRIVER=(sql server);Database=TestKSQL;Server=KSQL;Trusted_Connection=YES;

Do you know what I am doing wrong or what I need to do to get this to work?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thank you both so much.  It works fine on my test database.  You made my day!
Just wanted to add that I have successfully updated the production database that needed to point to the new server.  Thank you again for the help!