Need advice on Muli-User environment over a network

[dennisell]

I am creating a database for where I work and there will be around 10 different users and eventually up to 20.

I have split the database up into two parts, one that goes on each workstation that is the "Program" and one on the server that hold the data.

My question is: Is it recommended to break out the database on the server that holds all of the data into several databases rather than one big one, or does one way over the other effect performance?

 

[GDGarth]

I've done them both ways, and haven't seen a big difference in performance.

If you have a lot of data (close the the limits of Access), or if you're running automatic updates from several different sources, I'd split the data up. I've got a database that has one table with 500,000 records, and others with 10 - 20,000. Plus, it updates from a number of different sources every minute, 24/7. I've got that one split up. That way, I can lock people out of certain tables, perform maintenance, etc. without shutting down the entire application.

If you have a smaller amount of stable data, I'd just put it all in one spot.