1st time for deployment

[Guest]

It has been my first time setting up a database.
I am now wishing to share this database amongst other users who will be able
to user this database at the same time!!.

There is a Server and everyone else has there own PC.
As I understand it, the workgroup file must go on the server and then users
can create a shortcut from this?? Is this correct??

Thanks for any help.

 

[Chris Reveille]

Here is something from Larry Linson

For an overview of Access in a multiuser environment,
download my
presentation from http://appdevissues.tripod.com.
That will get you started with a list of topics that I
though worthwhile to
discuss with my user group.

For the most complete collection of information and links
on multiuser
Access that I know about, visit MVP Tony Toews' site,
http://www.granite.ab.ca/accsmstr.htm.

Chris

 

[Joan Wild]

It has been my first time setting up a database.
I am now wishing to share this database amongst other users who will
be able to user this database at the same time!!.

There is a Server and everyone else has there own PC.

Split your database into frontend (all objects except tables) and backend
(just the tables/relationships). Put the backend on the server in a folder
that all users have read, write, execute and delete permissions on. Give
each user a copy of the frontend, which will contain links to the tables in
the backend.

As I understand it, the workgroup file must go on the server and then
users can create a shortcut from this?? Is this correct??

If your database is secured, then yes this is the easiest way to maintain
the workgroup file. If it isn't secured, then this is unnecessary, as users
can use the system.mdw that's on their PC.