Software

Ask something
Discussion Locked

Access 97 security across a network

0 helpful
12 replies

by kpike2

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Access security across a network
I know how to set sign-on's for an Access 97 database and create some permissions (locally). When I access the same database from a remote computer, I get right in without having to sign-in. How do I get the permissions to spread to other PC's just for that one database? Is there anyone who knows how to accomplish this? Thanks!

From: kpike2@yahoo.com Date: 1/15/02 Status: Unanswered Points: 150

12 replies

by sl-campbell

Hi again,
The permissions do not need to be "Spread" to other PC's as you would think. The security permissions are stored in the MDB and only the Groups and User accounts are stored in the Workgroups db.

If the mdb was created with the default Admin account and the default admin account still has full permissions, then when the mdb is moved to another PC, anyone with a copy of MSAccess can open the mdb with the same (default) Admin account.

The secret is to create the mdb with after signing in with an account that you created, and that has full permissions. You need to create an owner and admin accounts with full permissions. The best for a EXISTING mdb is to create the owner account, create an empty mdb, import all the objects from the original MDB and change the ownership of those objects.

And, then create your own Admin account, naming it maybe PvtAdmin, and assign full permissions to it. (you can create your own owner and admin accounts using just one account instead oftwo different ones).

THEN, with the default Admin account you need to revoke the neccessary permissions, or revoke all permissions at best, and create a new admin account, maybe calling it UserAdmin, and assign it the highest level of permissionsthat you want all users to have.

Lastly, for an extra touch, do not give the Workgroup that you created the MDB with to other users.

I also explained this in another question -see the below thread:

(Make sure that there are no spaces in theURL or the page will not be found or come up at the wrong page)

https://www.techrepublic.com/forumqa/thread_detail.jhtml?thread_id=73566&src=bc

It sounds alittle troublesome, maybe because of my wording, but it really isn't. The main three things are:

1. Create your own Owner/Admin account with full permissions and change the ownership of all objects to this account.

2. Revoke permissions for the DEFAULT Admin acc

by sl-campbell

PS. before you attemp this with an important MDB, try it first by creating a small test mdb. It is simple an fast and gives you the idea of what needs to be done.

by sl-campbell

I just noticed that my answer got cut off because it was too long. So I am posting the last part again:

It sounds alittle troublesome, maybe because of my wording, but it really isn't. The main three things are:

1. Create your own Owner/Admin account with full permissions and change the ownership of all objects to this account.

2. Revoke permissions for the DEFAULT Admin account so no one else can just use the default Workgroup that comes Access and, using the DEFAULT Admin account, open your database.

3. Do not ship the Workgroup database file, that you used to create the mdb, with the distribution package.

Also, if you need more security, you can encrypt the mdb, but it slows things down some.

by shanghai sam

I understand that I need to revoke permissions for the default admin, but when I have another user sign-on at a different location, the user gets no option to sign-on. The default admin is automatic and there is no logon option and under the security screen there are no groups set that were originally setup. But the groups are still on my local computer. Please Help! Thank You. Kpike

by sl-campbell

Yes, but you still need to distribute to each location the workgroup - as I said above, only the permissions get stored in the MDB - not the groups or user accounts. The best would be to send a copy of the workgroup file, (again, not the one that was used when the mdb was created - start a new one with all the groups and user accounts).
Then, have the users JOIN that workgroup, or do it automatically (put the workgroup file in the same folder as the mdb and use a command line switch ? MyMdb.Mdb /wrkgrp File - to point to that workgroup when the mdb is opened)

by sl-campbell

I will get back in more detail later - (time bind).

The workgroup file, system.mdw, needs to be distributed - rename it and put it in the MDB folder and start the MS Access Workgroup administrator program in your MS Office folder, and have users join the copied Workgroup, or use the command line switch mentioned above to do it automatically when the users start the MDB application.

by sl-campbell

Ok. I am sending you an e-mail that I want you to check out first - then, once you have read the points you are welcomed to get back with me with further questions.

by kpike2

Where is all of these files located that you keep talking about? I could find the system.mdw (is this the file I need to copy) and if so how? The system.mdw currently is located at C:\winnt\system32. I got the database ready and it is working perfect (locally), but the networking and workgroup part is getting very confusing. Please explain in more detail where the files that need to be copied are and how/where I need to copy them. -Thanks-

This discussion is closed to new replies.