Multiple Users

[aussieolie]

I have a database that will be accessed by multiple users at one time, will I need to setup Users/Groups in MS Access for them to be able to work normally? Security is not an issue - as I have LAN security etc...
I just want to know if they will be able to use it without a username and password (or the default username Admin).

Thanks,

olie

 

[RichMorrison]

You wrote
<<
I just want to know if they will be able to use it without a username and password (or the default username Admin).
>>

Yes, you can put an MDB on a network drive and open it without username and password. This requires a System.MDW where the user "Admin" has a blank password.

This is what you should do:
copy an MDB to a network drive,
copy System.MDW to a network drive,
make a shortcut that launches MSACCESS.EXE and refers to the System.MDW on a network drive.

Distribute the shortcut to the end users.

RichM

 

[jeo]

I'm trying to set up the same thing. I'm wondering if you could explain in more detail of how to do this. I'm just a beginner and don't know a lot of how things work, but I'm trying to learn.

Thank you and sorry about inconveniences.
I really appreciate your help.

 

[RichMorrison]

Try a search using "network", "shared", "multi user"

There have been several threads on this topic.

That will be better for you than my solo response.

RichM

 

[aussieolie]

This will help you in specifiying where the MDW is located (which you will need to do if it is on a network share).

http://support.microsoft.com/default.aspx?scid=kb;en-us;209207
Pay particular notice to the /wrkgrp switch.

Olie

 

[sambo]

RichM..

You said..

copy System.MDW to a network drive,
make a shortcut that launches MSACCESS.EXE and refers to the System.MDW on a network drive.

What is the benfit/cost of these 2 steps? The method I currently use is simply to put the .mdb in a shared network folder and create a shortcut which everyone copies onto their own Desktop. This works just fine.

I guess I'm just not clear on where the System.MDW piece of the puzzle comes in.

 

[aussieolie]

It allows for multiple database usage, with multiple MDW Secuirty files.
Yes I also replicate shortcuts. but they still point to MDW's that way I never have to go to the workstation and change the settings under the 'Workgroup Administrator Utility' to specifiy where the MDW is.
In fact its better to use a local front end on the workstation and a backend on the server (with an MDW), thats another story I guess. Just better performance.

Olie

 

[RichMorrison]

Olie,

You wrote
<<
It allows for multiple database usage, with multiple MDW Secuirty files.
>>

I think it is best to use only one MDW for all applications on your network. That way all shared MDBs on your network refer to a common MDW with all groups and users.

This is much easier to administer when the number of applications increases.

RichM

 

[sambo]

I see..
So this method only deals with .mdb applications that have implemented MSAccess Security. That is where I was getting hung up. I have always just created my own user groups/security settings.

Thanks for clarifying..