Thanks

[Guest]

Hey thanks.
It sounds like Ive got to much action going in then..
This seperation will allow for thier own little data base?
See we need all the information to be gather together for our reports.
We have some people routing and updating and some people on the missed escalations..
I can see how this would reduce the stress on the one file though.
thanks alot it gave me many ideas to expand it.

 

[tina]

as Kevin says, splitting the db into front- and back-ends is the way to go
for a multi-user db on a server.
the backend db will have all the tables, so all your users' data will be in
one place.
the frontend (a master db for you to update as needed, with a copy of same
on each user's hard drive) holds all the other db objects - queries, forms,
reports, modules, macros, as well as links to all the backend db's tables.
make sure you put an actual copy of the frontend db on each user's pc -
don't just put it on the server and give each pc a shortcut to it.
good luck.