Link to home
Start Free TrialLog in
Avatar of markremms
markremms

asked on

MS SQL ODBC Connection String issue

Hi

Scenario:
1.  SQL Server 9.0 running on Small Business Server 2008
2.  Existing MS Access front end connected to MS SQL database using ODBC (original connection not created by me)
3.  This front end is in use by a number of users in the local network (using their own copies)
4.  I have added new tables to the back end SQL Server database and now wish to connect to them (I log in with a trusted connection).
5.  I create a DSN less ODBC connection to the back end tables (Trusted Connection) which works great for me logged into the server by RDP
6.  A test user (who is able to use the old version) on the local network attempts to connect using the new MS Access front end and gets an ODBC "cannot connect" error.

Working connection string on the old front end:

ODBC:DRIVER=SQL Server; SERVER=Servername,1433;UID=Username;APP=Microsoft Office 2010; Database=DatabaseName; TABLE=Tablename;

No one knows the backend database password.

What would be the best way forward?  The old connection string confuses me as it has a UID but no PWD.  Is it trusted or not?

Thanks
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 markremms
markremms

ASKER

Hmm.. If I do this won't I create a DSN?  Will it be necessary to distribute this to each user (or set up the DSN on each machine being used?)
Sorry for the late points.  had forgotten this was open.