|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
AllowBypassKey in Access projectDoes anyone know how to prevent users from displaying the DB window by
holding down the Shift key when opening an Access project? I want to stop users from viewing/editing tables directly from the DB window. Any help much appreciated. Jonathan Attree Jonathan Attree wrote:
> Does anyone know how to prevent users from displaying the DB window by For an Access project (ADP), you apply security in SQL Server or MSDE to> holding down the Shift key when opening an Access project? I want to stop > users from viewing/editing tables directly from the DB window. prevent users from accessing tables directly. For an mdb you apply User- level security, remove all permissions for tables except from members of the Admins group, use RWOP (run with owner permissions) queries so users can *see* data in forms, reports and queries only, and then run this code to prevent users from holding down the shift key when opening the database (and changing this setting): http://www.mvps.org/access/general/gen0040.htm. Note that if you don't apply User-level security, this setting can be reversed by anyone because the default Admin user in the default workgroup has the permissions to reverse it. -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/Forums.aspx/access-security/200611/1 Thanks for the reply.
How do I apply security in SQL Server to prevent users editing data directly? Re AllowBypassKey Found this which seems to work with Access projects: http://support.microsoft.com/kb/826765 Jonathan Attree Show quoteHide quote "Granny Spitz via AccessMonster.com" wrote: > Jonathan Attree wrote: > > Does anyone know how to prevent users from displaying the DB window by > > holding down the Shift key when opening an Access project? I want to stop > > users from viewing/editing tables directly from the DB window. > > For an Access project (ADP), you apply security in SQL Server or MSDE to > prevent users from accessing tables directly. For an mdb you apply User- > level security, remove all permissions for tables except from members of the > Admins group, use RWOP (run with owner permissions) queries so users can > *see* data in forms, reports and queries only, and then run this code to > prevent users from holding down the shift key when opening the database (and > changing this setting): http://www.mvps.org/access/general/gen0040.htm. Note > that if you don't apply User-level security, this setting can be reversed by > anyone because the default Admin user in the default workgroup has the > permissions to reverse it. > > -- > Message posted via AccessMonster.com > http://www.accessmonster.com/Uwe/Forums.aspx/access-security/200611/1 > > Jonathan Attree wrote:
> How do I apply security in SQL Server to prevent users editing data directly? It's too much for me to write the book myself in a newsgroup post, but youcan read everything about security in the BOL, which comes with SQL Server. If you use that you'll be pleasantly surprised when one of your users runs this line of code on your database: CurrentProject.Properties.Remove "AllowBypassKey" -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/Forums.aspx/access-security/200611/1 
Other interesting topics
|
|||||||||||||||||||||||
