Access 2000 Security with Access 2002

[Blorf]

Hi guys. This is beaten to death I'm sure, but I just don't get it.

I built security into a db that works just great on access 2000, but a user runs it with 2002 and it bypasses log in. I read enough after the fact to learn that it's due to the 2002 user loging in using his default secured.mdw workgroup file.

So knowing this, I have to ask, what do I do to prevent this? Microsoft site suggests that I made all the rookie mistakes possible, and here is how to fix it, so I will do that, but I still don't quite see what is happening here. What binds a d/b to a work group?

All I have read suggests that nothing does, and I know it can't be so poorly designed, meaning I am missing something.

Any insight would be most welcome.

Thanks,
ChaZ

There Are 10 Types Of People In The world:
Those That Understand BINARY And Those That Don’t.

 

[lupins46]

THere is nothing that links a workgroup and a database.
You decide which workgroup to use for each database.

If the security 'worked great' on A2000 it should work exactly the same on A2002 provided you use the same workgroup file.

You can get the details on how to set up security using the Access security FAQ from support.microsoft.com
It is not a trivial process and unless you follow the steps exactly you will not end up with a secure application.

When you have completed the process, you associate a workgroup file with a database through the desktop shortcut that is used to start the application.

"pathtomsaccess\msaccess.exe" "pathtodatabase\mydb.mdb" /wrkgrp "pathtoworkgroupfile\myworkgroupfile.mdw"

 

[Blorf]

Hi Lupins. I did recognise that I did something wrong, and I now know what the deal is. Turns out there is a flaw with the security wizard, per Microsoft's FAQ's. It also tells me how to clear it issue. I guess when I read it the first time, I missed it. I pasted the paragraph that explains it.

----

Additionally, you may need manually to remove the Open/Run permission from the database container for the Users group through the security menus or through code. This will prevent someone from opening the database by using another workgroup information file or the default System.mda/mdw. In Microsoft Access 97, the User Level Security Wizard is supposed to remove the Open/Run database permissions for the Users group, but fails to do so. The Access 2000 Security Wizard removes permissions to the point where they are not visible on the security menus, but testing has revealed that in Access 2000 it is possible to open a database by using the default workgroup information file regardless of the menu settings. The cure for both versions of Access is to create a new, empty database while logged on as a member of the Admins group and import all of the objects from the security-enhanced database. You should take this step before spending too much time helping protect objects because Access considers imported objects to be "new" and loses the permission information that was stored in the source database.



There Are 10 Types Of People In The world:
Those That Understand BINARY And Those That Don’t.