Question Creating User Accounts for database on shared folder

[knightjp]

hey guys,

I've just finished updating an access database which I uploaded onto a shared folder in a server.
Since there are going to be other people who will be accessing the database, I need to give them "Read-Only" rights, saving the editing features for myself alone.
I've tried to do it using the Security Wizard and it gave me a shorcut on my desktop. I copied the shortcut onto another persons PC and it worked. That person had the correct rights and everything. But a problem arose when a person with Office 2007 tried to copy the shortcut and use it. The shortcut seemed to be linked to my PC. Is that true? Since then, I've reverted to the backup and removed all security options altogether.

How do I create user accounts and passwords for the database while the file is on the shared folder?

Julz

 

[Dennisk]

Quite often when moving shotcuts from one PC to another Windoze in its wisdom changes the actual path that you can see in the shortcut properties.

Check the properties and re-specify if necessary.

Are all the versions of Access the same on each persons PC and are the paths to Access the same on all PCS.

 

[knightjp]

So far I have been trying to find a way to get it to work. I gone back to the old database without any security at all.
Could any please tell me a detailed procedure on how to get this working.

Please keep in mind that I want the database to run on the shared folder and not from any local system.
By this way, I do not need to do anything to start working say I have to use another PC in the network.

 

[DCrake]

Have you only one copy of the front end on the server that everyone is accessing? if so, this is not the norm. Each user needs to have a copy of the front end on their pc which links to the back end on the server. You could then test for the computer name of the client and if it is not yours then make your forms read only.

David

 

[knightjp]

Have you only one copy of the front end on the server that everyone is accessing? if so, this is not the norm. Each user needs to have a copy of the front end on their pc which links to the back end on the server. You could then test for the computer name of the client and if it is not yours then make your forms read only.

David

There should be way for me to do have multiple users accessing a single database.

Julz

 

[Rabbie]

There should be way for me to do have multiple users accessing a single database.

Julz

Yes you can have multiple users accessing a single database but be aware if you do you are increasing the risk of database corruption. Best practice to reduce this risk is to split the DB into FE/BE and give each user their own copy of the FE on their own PC. This also improves performance. There are good tools available to manage the versions of the FE. See Bob Larson's site for more details.

At the end of the day it is your DB and your decision on how to run it. Just be aware of the risks of sharing the FE database.

 

[DCrake]

Having a single mdb for all uses to use simultainiously is like playing musical chairs everybody is running around and when the music stops someone will fall over. Like wise the first person opening the database will define the settings, however then next person will attempt to rewrite the settings, ok they may be the same, but if not, you are going to get conflicts. they are both using the same jet engine and indexes even if they are looking at different records in the same table.