Solved

MS SQL ODBC Connection String issue

Posted on 2014-01-29
3
486 Views
Last Modified: 2014-06-20
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
Comment
Question by:markremms
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 84

Accepted Solution

by:
Scott McDaniel (Microsoft Access MVP - EE MVE ) earned 500 total points
ID: 39817724
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
 

Author Comment

by:markremms
ID: 39817762
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
 

Author Closing Comment

by:markremms
ID: 40146887
Sorry for the late points.  had forgotten this was open.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article we will learn how to fix  “Cannot install SQL Server 2014 Service Pack 2: Unable to install windows installer msi file” error ?
A Stored Procedure in Microsoft SQL Server is a powerful feature that it can be used to execute the Data Manipulation Language (DML) or Data Definition Language (DDL). Depending on business requirements, a single Stored Procedure can return differe…
In Microsoft Access, learn the trick to repeating sub-report headings at the top of each page. The problem with sub-reports and headings: Add a dummy group to the sub report using the expression =1: Set the “Repeat Section” property of the dummy…
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …

737 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question