Well, I think what you are asking is a very complicated question.
First you have split the dbs correctly, with Front End containing the Form, and linked tables, and the back-end containing the actual tables.
If you are going to design a database with multi-users, you are going to bet you have multi-user issues.
The FrontEnd Database you can change the forms at any time you want, and then just update each person's computer.
Then use some code to check that the linked tables actually exist where they are supposed to, and relink them automatically (i.e. let the user do it).
You can also do it manual yourself.
You only have to link the tables once on each computer to the server.
There is no issue with a conflict on the Front-End Forms, etc.
Only conflict is with the records called up in the Back-End.
In Access 2000, Record Locking is by default set in the Tools ==> Options ==> Advanced Tab.
Also you can individually fix this in each Form.
In Multi-User dbs you have to look at wether you need Row-Level Locking, or Page-Level Locking, or Pessimistic Locking.
I would look at the Forms (really the recordsets underneath them) and whether people will be changing the same Records.
If they are just adding records, then make it so that you use Data Entry on the Forms.
Otherwise, if you have say 1000+ records, there is no use to call them up just to enter.
So, again, multi-user databases need to be very carefully designed.
Some people put the local small tables, which don't change much on the Front-End, like propery tables, etc.
Hope this helps.
Database Agreements
|
