User Accounts Issues / bad set up

[rival]

Firsty, hey all!

I have recently set up a small stock system for my company, and during the last stages i was setting up the user groups and security settings.

Unfortunatly i am now in a position where i cannot modify anything at all! It seems i have set up the 'Admin' group, myself, with no permissions at all. i have one copy of the DB which has a database password, which i know, but no rights to change user privlages nor the ability to open exclusive. There is only one user set up - 'Admin'.

I also have another copy which has no DB pass, but fails to open due to access rights again.

I think i have made a real boo boo. Unfortunatly as all the tables, forms, queries and macros are protected i am unable to even import them into a fresh database without a complete rewrite.

Anyone got any ideas on this?

Thanks

 

[ColinEssex]

Sounds to me like you have a big problem

I'm not an expert on this but others are - so maybe they can help, just hang in there.

I think the golden rule prior to setting up workgroups is to take a copy of the database immediately prior to doing it - making sure of course you can access / copy / import everything to a new database if you screw it up.

Good luck

Col

 

[rival]

thanks for comments.

i dont even seem to have a .mdw file saved on my pc. The permissons must have been set up at some point and this file created in order for the DB to have premission restrictions. Yes i did use a wizard, never again.

Any, finally, yes, better planning would have avoided all this

EDIT, my bad the mdw files are present

 

[ColinEssex]

Just out of interest, another way of doing restrictions and limiting access is to have a UserName file (if the Db is on a network)

So when the person logs in, the Db checks the username file to match the network name to the file, if its not there then they get logged out automatically - they can't get past the opening screen, if they are there a message pops up saying its ok.

As for doing things when they get past the first check. They are allocated a letter (A,B,C etc) in the username table, the form opens and their letter is checked and the relevant properties of that form are changed to suit the level of access (can edit, can't edit, can add new, can't add new etc)

You can also enable/disable buttons on the opening switchboard screen so they can't go to certain places (like masterfiles or whatever)
Plus you can keep a log table of who logs in, the date and time and logout time and calculate how long they were in.

That way you don't need to bugger about with passwords or workgroups and you can still maintain security.

Col

 

[rival]

thats where my problems started. The DB worked fine on my pc, where it was designed, but when i tried to make it avalible to the network, and other local machines, errors started popping up, its then i think i made the errors.

And thanks for the alternative check methods, something i may try once i get things sorted. The worst thing is i cant even view anything in design mode ~(for this i could get the info quickly re rentered) even when i can gain exclusive access

 

[ColinEssex]

The errors were probobly due to missing references on the other PC's

Col

 

[rival]

issue resolved.

restored all mwd to original locations and got a copy to launch with the user login screen. Successfully logged in as user 'Administrator' and granted full access to any existing group while i sort things out.

Again thanks