security problem with network - only works on initial computer.

[mikelauwrie]

Hello all,
I hope you can help, as I'm a bit puzzled!

I have created a database (access 2000)(which is on a server) and secured it with the security wizard. This was before I knew anything about workgroups.

Through this securing process there was a workgroup file created in the same directory as the database (called secured). If I run wrkgadm.exe I find that I am using the 'system.mdw' standard workgroup. This I copied to the network directory of the database.

Now the security settings work on my computer - when I open the database a login box pops up and I can login in using any of the accounts that I created.

However if I try to login from another computer on the network I am not allowed to access the file (I don't get an option to login). It is worth noting that I changed the workgroup to the one that I copied from my computer onto the server.

This is my problem: if I disable the admin password, anyone can access the database without needing to login - no security. Or if I enable the admin password I can use the database I want to, but no one else can login - problem!

I hope someone can shed some light on this problem.

cheers

Mike

 

[KLewisBPM]

I think you need to join the new workgroup which you have created for each PC.

You can do this from within Access 2002

else 2000 you need to run the wrkgadm.exe.

Once you have found this you can than hit Join and point it to the mdw file on your server.



Kind Regards

Kelley Lewis

 

[JeremyNYC]

Mike,

You've definitely missed some steps. In cases like this, it's always best to go back to an unsecured copy, make another copy of it, and start from scratch.

My old website,

http://www.abcdataworks.com

has a walk-through of how to secure a database that's a bit more thorough than the one MS provides in their white paper. You have read that, right? If not, definitely read it (it's also on my site). And probably read it more than once.

You should never try to secure system.mdw, only a new workgroup. And really, it's best to never join any other workgroup than system.mdw. Instead, create a shortcut that points to msaccess.exe, your database, and the workgroup file. I think there's info about that on my site. If not, you can definitely find it by googling for it.

Jeremy

---
Jeremy Wallace
METRIX Project Coordinator
Fund for the City of New York

 

[mikelauwrie]

this is all very well and good. but a bit late.

I have tried connecting the other 'client' computers to the workgroup through the .exe mentioned - to no avail.

also I do not have an unsecured copy. if I did then I would be more than willing to do the whole thing again with a new workgroup, etc.

I have had a go at importing the objects into a new database. but have still had trouble getting the whole thing to work.

I suppose really I'm looking for one out of two solutions:

either I 'remove' the security that I have put on. and try again.

or I get what I've got to work properly. like I say it all works fine on my computer. it's only with others that problems arise.

n.b.
i have copied my system.mdw onto the server. and now both my computer and the others are running off this exact file (on the server).

cheers

mike

 

[mikelauwrie]

ok problem sorted.

I had to make a few adjustments to the shortcuts being used as well as some permissions/etc