When connecting using Access, you can either use a DSN that utilizes
the SQLS login you have created, or you can supply the connection
string in code from VBA. From a maintenance standpoint, connection
strings in code are recommended so you don't have to create a DSN on
every client machine. For ODBC connection string examples, see either
of these two resources:
http://able-consulting.com/ADO_Conn.htm http://www.connectionstrings.com -- Mary
Microsoft Access Developer's Guide to SQL Server
http://www.amazon.com/exec/obidos/ASIN/0672319446 [quoted text, click to view] On Tue, 2 Sep 2003 17:00:26 -0700, "bert" <bert_w@att.net> wrote:
>We are accessing SQL Server 2000 with a MS Access 97
>application using an ODBC connection.
> I have set up the ODBC driver and connected to the
>database using a SQL Server account. I have it set to use
>SQL Authentication using an ID and password entered by
>the user. I can connect and run queries for this account
>using Query Analyzer.
> When I try to connect using the MS Access application I
>receive the following error message:
>Connection Failed:
>SQLState: 28000
>SQL Server Error: 18452
>....Login failed for user '(null)'. Reason: Not
>associated with a trusted SQL Server connection.
>I click 'OK' on the button and then a window opens
>listing my ODBC data source, the Login ID and the 'Use
>Trusted Connection' box is selected. If I uncheck the box
>and enter a password I connect fine.
> How can I get the ODBC driver to present the login
>prompt without all of the error hoopla?
> Thank you, -bert