Mike & Doris Manning
mikedorism at adelphia.net
Fri Sep 17 13:23:01 CDT 2004
Easiest way is to use your Global Domain master account and use Windows NT authentication to set up a trusted connection to the server. Doris Manning Database Administrator Hargrove Inc. www.hargroveinc.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Christopher Hawkins Sent: Friday, September 17, 2004 2:06 PM To: accessd at databaseadvisors.com Subject: [AccessD] Connecting to SQL from Access w/a single login? This is driving me nuts. I know I did this a few years ago, but right now I'm totally stumped. A client of mine wrote himself an Access app for use around his office. Eventually the back-end swelled up to 500MB and problems ensued, so they decided to go to SQL Server. He upsized the database himself and then called me in to help get the Access front-end working against SQL Server. Here's my current issue; I want all the Access clients to use the same SQL Server login rather than having a unique SQL Server login for each domain account. I went ahead and created an AppUser login and gave it the appropriate permissions to the application database. I have the AppUser login and password set in the ODBC DSN. But whenever a user tries to connect, an error message appears stating that his domain login was not recognized by the SQL Server. It's not even paying attention to the AppUser info. I'm surfing BOL right now, but haven't yet figured out what I missed. And I know I'm missing something. Any suggestions? Respectfully, Christopher Hawkins Software Developer (559) 687-7591 http://www.christopherhawkins.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com