Eric Barro
ebarro at afsweb.com
Fri Sep 17 13:40:08 CDT 2004
Check SQL server authentication if it is Windows based or SQL based. User management in SQL server goes like this... 1. Create the login first under the Security section 2. Create privileges for the login 3. Create the user and associate it with a login --- Eric Barro Senior Systems Analyst Advanced Field Services (208) 772-7060 http://www.afsweb.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 11:06 AM 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 ----------------------------------------- The information contained in this e-mail message and any file, document, previous e-mail message and/or attachment transmitted herewith is confidential and may be legally privileged. It is intended solely for the private use of the addressee and must not be disclosed to or used by anyone other than the addressee. If you receive this transmission by error, please immediately notify the sender by reply e-mail and destroy the original transmission and its attachments without reading or saving it in any manner. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Users and employees of the e-mail system are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy. The company will not accept any liability in respect of such communication.