C
CJM
I have a database that a select few people will access via an access ADP
project (using Windows Authentication). Potentially anyone could open the
ADP file (though they shouldnt), but I would expect that they wouldnt be
able to edit the data unless I give them permissions in SQL.
However, it appears that anyone who opens the ADP file can edit the data via
this method.
I'm sure I must be missing something simple - why can all these people edit
the data? The only people with *any* explicit permissions are a web user,
the dbo, and a group of 'editors' - all of these are ok and are expected.
Is the problem in SQL - have I provided too much access to public users
somehow? Or does accessing the data through and ADP file change the way
permissions are assigned?
Thanks in advance
Chris
project (using Windows Authentication). Potentially anyone could open the
ADP file (though they shouldnt), but I would expect that they wouldnt be
able to edit the data unless I give them permissions in SQL.
However, it appears that anyone who opens the ADP file can edit the data via
this method.
I'm sure I must be missing something simple - why can all these people edit
the data? The only people with *any* explicit permissions are a web user,
the dbo, and a group of 'editors' - all of these are ok and are expected.
Is the problem in SQL - have I provided too much access to public users
somehow? Or does accessing the data through and ADP file change the way
permissions are assigned?
Thanks in advance
Chris