Multiple users on a server

[Guest]

Hi. We finally went live after so much help from the discussion group-
Thanks! We of course weren't exactly ready. But hey.

We are trying to find the best method to use the database among a handful of
users. We're a non-profit and have hand-me-down computers. Currently, we have
the database on a server but not everyone that can see the server can access
the db.

Are there "sharing" issues that we need to know about? We do have a
technical resource but he's not familiar with Access so I'd appreciate all
advice about entering data, compacting, splitting, all of things you wish you
had known... Thanks!

 

[BruceM]

I'll just mention the first thing that pops into mind, which is that the
users need read/write permission to the folder in which the database is
stored.
Splitting means putting the front end (the user interface) on each
individual computer, and the back end (the data) in a network location.
This is one link (there are a number of them out there) with more
information about splitting:
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm
Compacting is a maintenance chore that should be done from time to time
after backing up the file, especially if you have done a lot of editing or
deleting.
There's a lot more to all of this, but these are a few of the highlights.

 

[Douglas J. Steele]

The application should be split into a front-end (containing the queries,
forms, reports, macros and modules) and a back-end (containing the tables
and relationships). Only the back-end should be on the server: each user
should have a copy of the front-end on his/her hard drive. As well, each
user requires Change access (Read, Write, eXecute and Delete) to the folder
on the server where the back-end is located.

Of course, Access needs to be installed on each workstation.

 

[i_takeuti]

Hi. We finally went live after so much help from the discussion group-
Thanks! We of course weren't exactly ready. But hey.

We are trying to find the best method to use the database among a handful
of
users. We're a non-profit and have hand-me-down computers. Currently, we
have
the database on a server but not everyone that can see the server can
access
the db.

Are there "sharing" issues that we need to know about? We do have a
technical resource but he's not familiar with Access so I'd appreciate all
advice about entering data, compacting, splitting, all of things you wish
you
had known... Thanks!

 

[Guest]

Thanks for the tips!

The application should be split into a front-end (containing the queries,
forms, reports, macros and modules) and a back-end (containing the tables
and relationships). Only the back-end should be on the server: each user
should have a copy of the front-end on his/her hard drive. As well, each
user requires Change access (Read, Write, eXecute and Delete) to the folder
on the server where the back-end is located.

Of course, Access needs to be installed on each workstation.

 

[Guest]

Thanks for the tips and the link. The article scared me a bit but our
technical guy is ready to go!