Major Help Needed

[N1ck9141]

I have created a database on a shared drive...and using the normal access user and privliages tools ive made a admin and a user account

however it only works for the one pc i created it on, WHY

i need major help with this as there are about 2000 computers that all use the data base and i dnt have the time or man power to set up the privlages on each one please help

 

[KenHigg]

Here's the starters, it's just too complicated to go much futher into it in a forum thread.

When you install Access it uses the system.mdw file for default security and if no user name is provided when you start Access it will deault to 'admin'. Even if you have not touched any related to security this still happens. If you plan on using a shared database on a network with Access security you have to create a new .mdw file and put it on the server so that all of the Access front ends can get to it. Then in order for Access to know to use this .mdw file instead of the default system.mdw on the local machine you can either point to each from each workstation from within Access and tell it to use this file as the default or you can tell Access to use the server .mdw in the command line of the shortcut (see the /wrkgrp option here:
http://support.microsoft.com/kb/209207 ).

Hope this makes sense -

 

[N1ck9141]

ok thanks for all the help im looking into this however to the last pst

how do i create a new mdw file and how do i make my database link to that

 

[statsman]

For an excellent overview of Access security, go to:
http://www.geocities.com/jacksonmacd
download the first file – Security Paper by Jack Macdonald. It really is the best Access security guide out there.

After you have absorbed all of Jack's suggestions, start again on a copy of your unsecured database.

 

[boblarson]

I have created a database on a shared drive...and using the normal access user and privliages tools ive made a admin and a user account

however it only works for the one pc i created it on, WHY

i need major help with this as there are about 2000 computers that all use the data base and i dnt have the time or man power to set up the privlages on each one please help

If you are going to use the database for more than one user you need to SPLIT the database and give EACH USER a copy of the database on their machine. Before you say you don't want to touch each machine, let me assure you that you only need to install it once and then you can use a tool like the one I have on my website (free) to auto update each user's frontend when you make changes to the frontend master.

1. Split the database to a frontend/backend.
2. Figure out how to initially distribute the frontend to the users. You can choose to have them put it in a common file path (like C:\YourPath) or let them put it where they may.
3. You could then use my Frontend Auto Update Enabling tool to enable auto updating on the frontend. So, what would happen is this -
a. You put the master mdb file on the network in a shared drive accessible to everyone.
b. After enabling that mdb file for auto updating, you distribute the initial file to your users.
c. After distributing, you then can make any changes necessary to your frontend in the master location and change the version number in two tables (one in the frontend and one in the frontend that is linked to the table in the backend).
d. The next time your users open their frontend, the program checks to see if the version numbers match. If they do not, then the db will let the user know that their frontend is out of date, it will close, delete the old file, copy the new frontend from the master location on the network, and automatically reopen for the user.

Then, you never have to distribute again. All you have to do is just worry about making the changes to the frontend master.

See here for why you need to split:
http://members.shaw.ca/AlbertKallal/Articles/split/index.htm

See here for the auto updating enabling tool:
http://www.btabdevelopment.com/main/MyFreeAccessTools/tabid/78/Default.aspx