Problems with Security - Group Accounts, Group Permissions and Security Wizard

[birchw]

Hi, having never used the security features under the tools menu in Access 2000, I thought I'd experiment with them on a copy of my database. Or so I thought! Everything was going well - I successfully set up a new workgroup file, defined a new group, set permissions, user names, passwords, etc until I realised that whatever it is that I've done, every database I go into (including the master!), regardless of whether it was created by me or not, is prompting me for the same user credentials.

Firstly, how do I undo this! And secondly, how can I create this kind of security specific to the database it was intended for?

Any help most appreciated. Thanks.

[NeoPa]

Unfortunately, the security file (.MDW) is specific to an Access installation (on a PC) rather than to a database.
You should find the default System.Mdw on your hard-disk (unless you updated this one - not a good move experimenting without a backup). If not, then someone else's PC should still have a copy (otherwise a reinstall may be required).
Once you have the file back and available you need to run a program (WorkGAdm.Exe) to set it back up.
If you've set up permissions in your database to use accounts other than Admin or Admins then you may be in difficulty.

[birchw]

Thanks NeoPa. Looks like I'm going have to reinstall. Thanks for your help.

[NeoPa]

If you just need a default copy of System.Mdw then reply here and I'll post a copy in this post.
Well, I tried but it's too big - Sorry :(

[birchw]

Thanks. Just one problem though... I've run a search and there are no *.mdw files at all on my C: drive - there is however an mdw file in the same folder as my database, called Secured.mdw, which is located on a network drive.

[birchw]

No problem, thanks for trying. I'll see if I can copy one from someone else's machine.

[missinglinq]

You couldn't locate the file running Find because the file's Hidden Property is set. You need to go wherever your version of Windows keeps the Folder Options and set the Show All Files option, then run Find again.

[NeoPa]

Thanks. Just one problem though... I've run a search and there are no *.mdw files at all on my C: drive - there is however an mdw file in the same folder as my database, called Secured.mdw, which is located on a network drive.

That's not hopeful :(
This solution relies on them just changing the password for the Admin account.
If they don't even use the Admin account this won't help you I'm afraid.

[birchw]

Thanks MissingLinq, that resolved that issue. I have two versions - one in C:\windows\syst em32 and another in c:\program files\common files\system. I replaced them both with a copy from someone else's machine, but the original issue is still occuring. If I delete the secured.mdw file from the network drive where my database is, I then get an error stating 'Microsoft Access could not find file system.mdw. This file is required for startup'. I.m guessing that it's just in the wrong place on my C: drive?

[NeoPa]

If you run the shortcut (Workgroup Administrator) this will tell you which MDW file is being used for that particular PC.
I suspect you will find that it points to your 'Secured.Mdw' file on the network and, as per post #8, that if you replace this file (renaming original rather than losing it completely) with a standard System.Mdw but renamed to Secured.Mdw then it will also fail. Try this anyway (or redirecting to the standard System.Mdw using Workgroup Administrator.

[birchw]

I don't seem to have Workgroup Administrator (or at least it's not under Tools, Security) - is there any other way I can access this?

[NeoPa]

See post #2.
You need to search for a program called WorkGAdm.Exe on your C: drive.
It should be somewhere from your Start button but it moves depending on version so...

[birchw]

Problem solved. It was indeed pointing to the secured.mdw file on the network drive.

Thanks once again for your patience and support.

[NeoPa]

Not a problem.
I'm glad (if a little surprised) that was able to help you sort the problem.
Surprised, only because I thought the security may have been set up more tightly with a name like Secured.Mdw.