Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Security Problems Again!!!

Status
Not open for further replies.

pfenton

Technical User
Jul 18, 2000
32
GB
I need help with a security problem!
The problem is that my d/b is to be placed on a read-only (to others)folder on the NT server. When this was done first the permissions for the folder hadn't been set-up right, so I went messing with security on the d/b using the Workgroup Administrator thing! Now though, the folder on the server has been correctly secured but I've got problems with my d/b.
Only 1 person can access at a time (shared is ticked!)and I'm not sure as to my next step!
Do I need to do something with the 'wrkadm' thing or can I get rid of it altogether?? The security on my d/b is not now needed because the folder security should be enough! HELP
I've created users permissions, an admin a/c etc... but still only 1 person can get on the d/b. What permissions should be allowed for users - I've given them: read design, read data, insert and delete data????
 
Berik
I've done that already as well as open/excelusive for myself (I needed to for making design changes).
I've also connected someone else to the wrkadm a/c but when they tried to open the d/b, they were that the file was already in use???
What's going on at all??
Big bundle of help needed somehow!
 

I'd suggest you remove your security in the database/workgroup file.

The easiest way to do this is to create a blank database while joined to the default workgroup (c:\winnt\system32\system.mdw c:\program files\microsoft office\office\1033\system.mdw) depending on OS and Access version). Then rejoin your workgroup and open your database. You should be able to export all components to the new database.

Once exported, rejoin the default workgroup file, open the new database and check that Admin owns all the objects. I suspect it won't but as the workgroup file is default, you will be able to change this by using the Change Owner option.

Hope this helps...

Austin
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top