Security stopped working

[Jens Burup]

I have VB.net application using an Access2000 database with Design master,
Hub and 4-5 local replicas on client machines Internet replication, and for
6 month security worked fine.
For some reason I had to make a new design master, and I looked at my notes
how I secured the database 6 month ago, and followed these instructions
again to protect my new database.
Now security won't work.

As soon as I switch workgroup to system.mdw or the database land on a client
machines using system.mdw, the database can be opened even without it is
prompting for a password, and if I then look in security user and group
accounts my own admin has disappeared??

If I switch back to my own workgroup again, I can see it my own account
again.


I believe I followed all steps descried in these fine articles:
http://www.jmwild.com/AccessSecurity.htm
and Access Security FAQ
1. What are the steps to help protect a database?



Any ideas what I did wrong here, are much appreciated.

Jens

 

[Rick Brandt]

I have VB.net application using an Access2000 database with Design master,
Hub and 4-5 local replicas on client machines Internet replication, and for
6 month security worked fine.
For some reason I had to make a new design master, and I looked at my notes
how I secured the database 6 month ago, and followed these instructions
again to protect my new database.
Now security won't work.

As soon as I switch workgroup to system.mdw or the database land on a client
machines using system.mdw, the database can be opened even without it is
prompting for a password, and if I then look in security user and group
accounts my own admin has disappeared??

Accounts reside in the mdw, not in the mdb. Why would you expect to see
your custom account in a different mdw?

If I switch back to my own workgroup again, I can see it my own account
again.

Yes, just as expected.

I believe I followed all steps descried in these fine articles:
http://www.jmwild.com/AccessSecurity.htm
and Access Security FAQ

No, you didn't. Try again. Don't feel bad though. You are only the 11ty
millionth person to attempt security the first time and get it wrong
When done properly, you will not be able to open the mdb without using the
appropriate mdw.

 

[Jens Burup]

No, you didn't. Try again. Don't feel bad though. You are only the 11ty

millionth person to attempt security the first time and get it wrong
When done properly, you will not be able to open the mdb without using the
appropriate mdw.

Rick

In fact I succeeded first time, 6-month ago-

To day I made a new 1 table database 1col 1 row for testing, and ran the
security wizard.

Despite Joan Wild advise not to use it for Access 2000 (sorry Joan if I did
not understand your article completely, English is not my born language)

It worked-

Then I imported my old database tables, and security is OK again.

Jens