Charlotte Foust
cfoust at infostatsystems.com
Tue Nov 25 16:11:40 CST 2008
If your client has an IT department, they are currently screaming bloody murder over that idea. It means you're leaving your SQL Server database at the mercy of any user who logs onto windows and then goes for a long coffee break leaving someone else to poke around in their machine. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters Sent: Tuesday, November 25, 2008 9:58 AM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Using Windows Authentication with Access/SQL Apps I'm working on upsizing one of my customers to SQL. They have asked if we could eliminate the Access workgroup username and password login that I currently use (mostly just so the database knows who is logging in). With SQL using Windows Authentication, my Access app could simply pick up on the current username and go from there, without going through an additional username and password entry. Has anyone done this? Any pros, cons, or gotchas? Thanks! Dan -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com