G
Guest
Hi,
I have a fairly large adp project, but now I need to apply some Form-level
security. There are 4 SQL Groups with a User connecting to SQL via
NT-security. Is it best to use SQL to stop user access to Views or to create
new views with limited data for each Group.
My problem is that my adp Forms have all fields present, whereas applying
the new security Groups some of the Forms fields are now sensitive. I guess I
can look at vba to check login and hide fields that they shouldn't see, but I
think this will be very time consuming.
The only option, i can see, is to create duplicate sql Views (not showing
sensitive data) and apply SQL security to each View.
Is this the best way to do this or do I have my 'blinkers' on.
Thanks.
Alan
I have a fairly large adp project, but now I need to apply some Form-level
security. There are 4 SQL Groups with a User connecting to SQL via
NT-security. Is it best to use SQL to stop user access to Views or to create
new views with limited data for each Group.
My problem is that my adp Forms have all fields present, whereas applying
the new security Groups some of the Forms fields are now sensitive. I guess I
can look at vba to check login and hide fields that they shouldn't see, but I
think this will be very time consuming.
The only option, i can see, is to create duplicate sql Views (not showing
sensitive data) and apply SQL security to each View.
Is this the best way to do this or do I have my 'blinkers' on.
Thanks.
Alan