Definitely possible, but it's highly recommended (in the interest of
database integrity) that you split your application to a Front End and
Back End. The back end holds all the tables (only), and is placed on
apublic folder on the network so all users can access it (full rights
required). The Front End holds all other objects (queries, forms,
reports, macros, code) and links to the tables in the Back End, and each
user should have a copy of it on their local HDD. Not splitting or
giving users separate FE copies is known to result in frequent corruptions.
How to get there: there is a built-in wizard in Access to help you do
this: Tools > Database Utilities > Database Splitter. It's so simple it
will be completed in a couple of minutes. Just make sure you store the
back end at its final location (network folder) right away, so you don't
need to manually change links later; yet, if required, you can easily do
so through Tools > Database Utilities > Linked Table Manager.
After completing the split, you can give each user a copy of the front
end, though it would be a good idea to convert the FE to an .mde and
distribute that, so the users have limited access to the design. To make
an .mde, go Tools > Database Utilities > Make MDE File. Make sure you
keep the .mdb, because if you need to make changes you will only be able
to do so in the .mdb, not the .mde!
A couple of useful links:
http://www.granite.ab.ca/access/performancefaq.htm
has some very good tips for improving split database performance, and
http://www.granite.ab.ca/access/autofe.htm
has an excellent utility for automated distribution of the FE, so you
don't need to go to every user's PC every time you make some changes to
your FE.
Tony Toews is to be thanked for both.
It would pay to spend sometime browsing in the multiuser newsgroup,
you'll likely find many answers there.
Finally, before you try anything you're not 200% sure of, *make a backup
copy* !
HTH,
Nikos
