Faris,
For true and less corruption-prone multiuser operation, your database
needs to be split into a Front End and Back End. The BE holds only the
tables, the FE holds everything else, with links to the tables in the
BE. The BE is stored in a public folder on the sever, where all users
need full rights to, while each user must have their own copy of the FE,
preferably on their local HDD. If you employ such a scheme, you should
be able to have several dozen users entering data at the same table(s)
at the same time.
Note: the form(s) don't store data, they are just an interface for the
user to store the data in the table(s).
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
