[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 520
  • Last Modified:

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
0
markremms
Asked:
markremms
  • 2
1 Solution
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
It's not Trusted. A Trusted Connection would look something like this:

Driver=SQL Server;Server=ServerName;Database=DatabseName;Trusted_Connection=yes;

However, the connection you show is from Access. To create that, you should use the Linked Table Manager in Access to relink your tables, or delete the links from your FE and recreate all of them using a Trusted Connection. You can do that using the External Data - ODBC item on the ribbon. When doing this, you can tell Access to use a Trusted Connection, and you can select all tables that are needed in the database.

Be warned, however, that your server will need to be configured to allow Trusted Connections (or Mixed Authentication). If it's not, and you delete the links, you're dead in the water unless someone there can supply you with the password.
0
 
markremmsAuthor Commented:
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?)
0
 
markremmsAuthor Commented:
Sorry for the late points.  had forgotten this was open.
0

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now