Right...sort of...
denileigh said:
You mean keep all the tables in one on the server and the forms, etc (linked tables) on their harddrives right?
If you have a decent Access resource text, "SPLIT DATABASES" will be covered. You want to follow this to employ at work.
Basically, a split database is EXACTLY what it sounds like. It is split in two parts.
The first part database (BACK END) contains all the table data and only the table data; no other objects at all.
This back end then lives on the Server.
The second part database (FRONT END) contains everything else and features links to all of the tables in the BACK END but this is the difference between what you're talking about and a true SPLIT DATABASE...
VERY IMPORTANT: The FRONT END part also lives on the Server and
copies of it are then placed on each of your user's PC's...that why I said everyone has their own unique front end but as the Administrator, YOU must use the ORIGINAL front end and make your structural changes and design changes to it so that when you update all of your user's FRONT END version, they will reflect the changes you made on the original copy.
Think of it this way, everyone else is just "borrowing" the database for their uses but you control and continue to develop the MASTER version of the database using, the original split FRONT END. Everyone is writing to the same BACK END and naturally, you don't want copies of it anywhere!
Again, extremely important, when you need to make a change to the BACK END database or when you are updating everyone's front end copy, copy each one, one-at-a-time, and when you are doing administration work in the database, make sure no one enters the application by running their front end or the whole database will become corrupt or even CRASH!!!
It's that whole, Exclusive Rights thing and can be volatile to say the least if not used correctly in these circumstances!
It's relatively easy to manage but I'm "alarming" sounding because I've had users break into the front end and destroy the database and rebuilding it from scratch when everyone needs it is super STRESS with hair on it!?#?$?!$
My favorite reference is the
Access 2000 Bible. If you need a copy, let me see what I can find for you to save you money but either way, as soon as you can, GET THIS TEXT because it has an excellent description of a split database!
For now, check out:
http://www.nwarwick.co.uk/AccessSplitting.htm
Or:
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm
And:
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm