Moving database to a network

[aids2]

This may seem to be a simple job but I cant seem to get it to work.
I have a database that is used by aprox 10 users. I wish to place this database on a network and implement full security.
However when I move it to the network how do I set up the security levels.
I have the system working on my PC but when I move it to the network the database wont open.
Any information you can provide me would be greatly appreciated.

 

[redwoodly]

There are a lot of variables here that can cause problems.
All you say is that is doesn't open. More information would help, such as..Do you get any kind of an error message? or your computer just sits there?....

1st place I'd look is at the server security/permissions.
Everyone that is going to use the db HAS TO HAVE READ/WRITE/DELETE priviledges to the folder where db is located (in order to create and remove the .ldb files).

 

[aids2]

Sorry for not explaining myself properly.
I can set up the security permissions on my PC but when I move the .mdb file to the network the database wont open becuase the security was not set up on the network.
What files do I need to move to the network apart from the mdb file, in order to get the security working.
I used the security wizard to set up all the security on my PC. Any information would be gretaly appreciated.
I cant get into the database at all becuase it doesnt recognise my password or user ID.
I hope this explains this problem better.

 

[redwoodly]

ok.
the most critical file is the .mdw (security file) file that you used to create the db with (and set up the security with.) This has the groups and users defined in it.

Do you know about this file? (this can be a lengthy explanation...so let's identify the problem first and then I'll explain).

Can you provide the exact message you get when you try and get into the db on the server?

The two most common problems are:

1. you don't have read/write/DELETE priviledges on the server FOLDER where the db is located.

2. When you try and access the db on the server, are you using a different PC to access the db ?(a different PC other than the one that has the db on it and does open the db.) if so, then I bet the problem is that you haven't "joined" the correct workgroup / .mdw file. and I can solve that problem.

a quick synopsis of what the fix to #2 is:
you copy the .mdw file that you used to create the db to the server.
Then you join the .mdw file (or WORKGROUP) using the wrkgadm.exe file on your computer. then you should be able to get in.
i'd be glad to explain more if this is the problem.
(you can email me at parnelll@saic.com if you need quicker response. I read that one during the day. )

 

[aids2]

Thanks for the information. I will try that and get back to you with an answer to see if it worked.
I wasnt sure about the mdw file. I figured that I needed to move it so that I could join it later.
I must assume that all of the people that use the Database need to do exactly the same thing and join the .mdw file as well?

 

[redwoodly]

Correct. everyone needs to join the .mdw file.
(note: if you have WinXP you don't use wrkgadm.exe file. WinXP has the utility under the TOOLs menu.)

 

[psemianonymous]

Please don't use WRKGADM.EXE to make everyone join the custom MDW file. It will work, but it also requires that any time they open Access, for any reason, they're prompted for a security login.


My preferred method is to give everyone a shortcut on their desktop that opens MSACCESS.EXE to your database file, with the special /wrkgrp command-line argument. This way, when they open Access regularly, they get no security login. However, when they use the shortcut, they go straight to your database w/ login required. Neat and professional.

Here's an example of what one might look like:

(this would go in the target line of your "New Shortcut&quot

"C:\Program Files\Microsoft Office\Office\Msaccess.exe" "C:\atemp\trn\trndb.mdb" /wrkgrp "c:\atemp\trn\trndev.mdw"

 

[fredk]

Foolio - I have a database that I have up and running for about 2 years - As I have learned, I have upgraded the database - I never implemented security for two reasons, the first is that I did not understand it The second is that the users are responsible and would not do anything they should not do.....- When I tested it on a sample database, I would run into the problem you explained, whenever anyone on the server tried to go into an access database, they got the message for a password.

I have the backend database in one folder and I have each front-end in another folder all on a shared network drive. If I create a shortcut for each user as you suggested, would I be ok? Also, what would happen if someone goes into the database without using the shortcut.

Thanks much for your advice.

Fred

 

[psemianonymous]

--If you get security done right, they shouldn't have access to any data if they don't use the custom workgroup. So if they double-click on the backend, they shouldn't even have the rights to view the database window, so they can't even open the database.

--The backend database is immaterial when dealing with shortcuts--it is linked by table links, which are stored in the frontend. So I should be saying, set your frontend to be the "document" the MSACCESS opens.


--You would (hopefully) only create one shortcut. Get it working right, then copy it to the network and from there to your users' machines.


I hope I got all this right.