|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Access security behavouris joined to security.mdw and the Unsecured are joined to system.mdw. After I log on to the secured DB, all unsecured DB's request user name and password. on cheking the work group of the unsecured DB's They have changed to Security.mdw. If I change the unsecured DB workgroup to system.mdw, the secured DB does not request user & password but errors with " You do not have permissions to use the 'xxxx.mdb' object have your system administrator..." If I then create an empty database and join it to Security.mdw close it and then open the secure DB all works OK again (except the unsecured are now secured again). I can create shortcuts to the DB's (access path, DB path, /wrkgrp work group path) and all DB's work as should do. Does anyone Know If this is the norm for Access to change the security for all DB's when the work group for one is changed or have I got some weird config. in operation. MS office 2003 with SP3 & XP Pro SP3 -- Thanks in advance for your help Regards, DaveJ "DaveJ" <Da***@discussions.microsoft.com> wrote in message No they're not. Your MS Access session is joined to a workgroup, the news:4B7C76CF-6A27-4CA0-AF92-9320210E3245@microsoft.com... >I have several unsecured Access databases and one secured DB, the secured >db > is joined to security.mdw and the Unsecured are joined to system.mdw. > default being system.mdw. You should leave this default setting and group alone. > After I log on to the secured DB, all unsecured DB's request user name and No they haven't, what you're seeing is the *default* workgroup which you > password. on cheking the work group of the unsecured DB's They have > changed > to Security.mdw. have changed to Security.mdw. As previously stated, you should leave the default as an unmodified system.mdw. > If I change the unsecured DB workgroup to system.mdw, the This is normal behaviour because you have joined the default workgroup. It > secured DB does not request user & password but errors with " You do not > have > permissions to use the 'xxxx.mdb' object have your system > administrator..." goes to prove that your secure db has been secured correctly. Show quoteHide quote > Nothing is being changed in your un-secured dbs. Security authentication is > If I then create an empty database and join it to Security.mdw close it > and > then open the secure DB all works OK again (except the unsecured are now > secured again). > I can create shortcuts to the DB's (access path, DB path, /wrkgrp work > group > path) > and all DB's work as should do. > > Does anyone Know If this is the norm for Access to change the security for > all DB's when the work group for one is changed or have I got some weird > config. in operation. > always performed first, even when you're joined to system.mdw, it just does it silently because it's wide-open. Your shortcut method with the /wrkgrp switch is the correct one so, in a nutshell, you're doing everything right. Have a read of the FAQs, link on my web site. Keith. www.keithwilby.co.uk Thanks Keith
Not what I expected, but most helpfull, I now have a much better understandin of how it works. -- Show quoteHide quoteThanks in advance for your help Regards, DaveJ "Keith Wilby" wrote: > "DaveJ" <Da***@discussions.microsoft.com> wrote in message > news:4B7C76CF-6A27-4CA0-AF92-9320210E3245@microsoft.com... > >I have several unsecured Access databases and one secured DB, the secured > >db > > is joined to security.mdw and the Unsecured are joined to system.mdw. > > > > No they're not. Your MS Access session is joined to a workgroup, the > default being system.mdw. You should leave this default setting and group > alone. > > > After I log on to the secured DB, all unsecured DB's request user name and > > password. on cheking the work group of the unsecured DB's They have > > changed > > to Security.mdw. > > No they haven't, what you're seeing is the *default* workgroup which you > have changed to Security.mdw. As previously stated, you should leave the > default as an unmodified system.mdw. > > > If I change the unsecured DB workgroup to system.mdw, the > > secured DB does not request user & password but errors with " You do not > > have > > permissions to use the 'xxxx.mdb' object have your system > > administrator..." > > This is normal behaviour because you have joined the default workgroup. It > goes to prove that your secure db has been secured correctly. > > > > > If I then create an empty database and join it to Security.mdw close it > > and > > then open the secure DB all works OK again (except the unsecured are now > > secured again). > > I can create shortcuts to the DB's (access path, DB path, /wrkgrp work > > group > > path) > > and all DB's work as should do. > > > > Does anyone Know If this is the norm for Access to change the security for > > all DB's when the work group for one is changed or have I got some weird > > config. in operation. > > > > Nothing is being changed in your un-secured dbs. Security authentication is > always performed first, even when you're joined to system.mdw, it just does > it silently because it's wide-open. > > Your shortcut method with the /wrkgrp switch is the correct one so, in a > nutshell, you're doing everything right. > > Have a read of the FAQs, link on my web site. > > Keith. > www.keithwilby.co.uk > > "DaveJ" <Da***@discussions.microsoft.com> wrote in message It's a tricky topic if you're new to it but once the penny drops you'll news:7B10B157-B066-4D18-8BB6-0CE6A5C5A127@microsoft.com... > Thanks Keith > Not what I expected, but most helpfull, I now have a much better > understandin of how it works. > wonder what all the fuss was about. The FAQ is essential reading and you'll see time and again on this group the advice that it's "all killer and no filler". You must follow all steps in the order stated, omitting nothing no matter how trivial it might seem. Good luck. Keith. www.keithwilby.co.uk
Understandable documentation regarding Access DBA security
Unable to compact/repair because I have it opened Access Networking & Security Issue. users set their own password Read-Only Database! Need Help With Security After migrating .mdb to v.2007 & rename mdw file, v.2007 lets me i Upgrade a password protected database Allow a Disk as a Trusted Location or disable it entirely Need help with creating MDE file |
|||||||||||||||||||||||