[AccessD] SQL Server as a BE

In SQL Server they have "Roles". You can still use your Windows Authentication but you will have to set up a userid on the sql server for each user and then assign them a role. You can set up an Access form to assign people roles and pass the T-Sql to set them up through a pass through query.
 
May God bless you beyond your imagination!
Lonnie Johnson
ProDev, Professional Development of MS Access Databases
Visit me at ==> http://www.prodev.us




 




________________________________
From: jwcolby <jwcolby at colbyconsulting.com>
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Sent: Tuesday, May 19, 2009 7:14:26 AM
Subject: [AccessD] SQL Server as a BE

One of my old clients had a company migrate their database to SQL Server.  They were told they 
needed to do this for HIPAA compliance, so that they could easily encrypt personal information.

Well... they told my client that they would never even know that it had happened and of course... 
things are broken, which the company is now trying to blame on Access.  Bottom line, they are now 
being fired and I am coming back to pick up the pieces.

I have only used SQL Server with small databases (which this is) and in those cases I used Windows 
Authentication.  If they used SQL Server group / user can you give me a very basic rundown on how 
this would work (general terms).  I understand the user / group metaphor, I have just never applied 
it to SQL Server.

Inside of my existing SQL Server databases I use Windows authentication and my objects all require 
dbo to access.  What happens if groups are used?

I do love the "learn under fire" scenario.

-- 
John W. Colby
www.ColbyConsulting.com
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com