User-Level security not working on shared Access2K DB

[PLSM]

Hi.

I have a shared access DB. It has user-level security set up, which is working on one PC but not on another. On one PC you can see user accounts and the permissions are working fine. On the other PC you can't even see the user accounts.

I have created a unique workgroup file but that does not seem to matter at all.

Does anyone have any idea what is going on?

Brgds,
PLSM Brgds,
PSLM

 

[KornGeek]

I'm guessing you did not remove permissions from the admin user and/or the Users group. Because this user and this group appear in all .mdw files, if they have permissions, then anybody can get into the database. Search through the older posts on this forum and the FAQs for some great info on Access security.

I believe JeremyNYC has a good paper on Access security on his website

http://www.AlphaBetCityDataworks.com

in the Developers' section. Step through the security document carefully, and it should help explain the process.

Access security is a complex system, and requires a careful process, but in the end is pretty good and (in my opinion) worthwhile. Don't be intimidated by it. Each time you work with it, it gets easier.

 

[perrymans]

Just because you make a new .mdw, you still have to point to it for the DB to use it. Read the MS FAQ and JeremyNYC articles. Make a shortcut to point to the new .mdw.

Also, by default, users log in a Admin (when you use your own version and no pop-up for username or password, it logs you in as Admin). This is the reason to REMOVE the ADMIN USER (not the ADMINS group) from the ADMINS group to the USER groups.

Sean.