They don't seem to work with SQL Server Security - does anyone use them?

Adam
* Keep up-to-date by attending the monthly meetings at the 'Access/SQL
Server/ASP.Net User Group, Sydney"   www.ssw.com.au/AccessUG
--------------------------------------------------------
Check out these HOT UTILITIES FOR ACCESS AND VB DEVELOPERS....
www.ssw.com.au
* SSW Data PRO  - Version Control for your data.mdb
* SSW Data Renovator  - Compare the differences between two data.mdb's
* SSW Upsize PRO! - Don't UPSIZE to SQL Server without it
* SSW SQL Script Wizard - A utility to run .sql files
* SSW Performance PRO! - Find out what is slow in your Access App
* SSW Contactor - An Outlook 2000 and 2000 Add-in
--------------------------------------------------------

 "Driver={SQL
Server};Server=SQLServerName;Database=pubs;UID=sa;PWD=sapassword"

should work.

The OLE DB connection would look like:

"Provider=SQLOLEDB.1;Data Source=SQLServerName;Initial Catalog=pubs;User
ID=sa;Password=sapassword"

--
Bob

------
Please do not send email directly to this alias. This alias is for newsgroup
purposes and is intended to prevent automated spam. I've been "encouraged"
to share this helpful information from our lawyers. This posting is provided
"AS IS" with no warranties, and confers no rights. You assume all risk for
your use. ? 2001 Microsoft Corporation. All rights reserved.

He's got the appropriate strings for both ODBC and OLE DB for both trusted
and standard security, as well as a couple of useful links to MSDN related
to this.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele