Re: Access Front End and SQL Server 2000 Record Level Access Control
From: Kevin3NF (KHill_at_NopeIDontNeedNoSPAM3NF-inc.com)
Date: 04/23/04
- Next message: Amol Kasbekar: "Re: Field Value"
- Previous message: Zach Wells: "Re: SQL Errors in Stored Procedures"
- In reply to: Noloader: "Access Front End and SQL Server 2000 Record Level Access Control"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 23 Apr 2004 15:10:34 -0500
1 is the closest answer, and you can code out any access to the underlying
tables/views via the Tools>>Startup options and some code I can't find right
now that disallows the use of Shift when opening the db. Couple that with
the very solid security built into the SQL Server and you should be able to
stop all but the most determined individual. In his case, you have more of
an HR issue than application.
2 breaks all sorts of rules.
-- Kevin Hill President 3NF Consulting www.3nf-inc.com/NewsGroups.htm www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs. "Noloader" <noloader@yahoo.com> wrote in message news:6b543aa7.0404231100.3d1dac62@posting.google.com... > Hello, > > We are using Access ADP as a front end, SQL Server 2000 as a back end. > We have a customer contact database. We would like to limit certain > users to only receive certain records based on Windows NT group > membership. > > For example, Eastern Sales Group can see clients located in their > region, but they cannot see clients located in the Northern Region. > > Is there an elegant way to do this? Below a two solutions which have > been proposed, but none seem to fit. > > ********* > ** 1 ** > ********* > Add an additional attribute (bit mask value) to tblCustomers, and > query appropriately based on the user's group membership. > > Problem: > Access allows users direct access to the underlying table. > > ********* > ** 2 ** > ********* > Create a separe table for each group (effectively splitting > tblCustomers into smaller, separate tables based on group access). > Then, apply SQL Server security on the objects to enforce the business > rules. > > Problem: > Does this break Normal Form??? I've never seen a solution like this. > > I've googled and found similar questions, but not a good solution. > > Any suggestions would be appreciated. > > Thanks, > Jeff > Jeffrey Walton > noloader.at.yahoo.com
- Next message: Amol Kasbekar: "Re: Field Value"
- Previous message: Zach Wells: "Re: SQL Errors in Stored Procedures"
- In reply to: Noloader: "Access Front End and SQL Server 2000 Record Level Access Control"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
