Does splitting DB necessarily boost performance

[Powderfinger]

The size of the db file is 80 meg and it is not currently not split. If I
split it , it breaks down to 2 meg code, and 78 meg tables.

I know there are other advantages to splitting a database, but right now I'm
only concerned about performance. Would splitting the DB and copying to each
workstation the code part , leaving only the data on the server, improve
performance much?

(4 workstations, 1 server, access 2000)

Thanks,

Jack

 

[Albert D.Kallal]

Often, you see little change. However, that sure is a nice small application
you now have.

And, often, there is a small performance hit, since now ms-access have to
open two parts. (but, you do save your network load here).

Since your application part is now only 2 megs in size, then you might not
see to much of a change. But, still welcome in terms of reliability.

If you had no problems, then likely you can say with your setup. However,
having the software separated from the data really does help you maintain,
update, and work on the next great version...

For your setup, the reason of reliability would likely outweigh the
performance issues.

 

[Guest]

Even with just four workstations, and only one person working on writing
forms and queries, it can be not uncommon to discover that some user has "Put
Access into a state" where you can't change anything. Apparently Access
sometimes decides that a user who is just entering data into a form is
altering the underlying form or query in some way. The fact that they did
not have rights to do so, and were not in fact doing so, does not change this.

This makes no difference in the moment-to-moment performance of the
computer, but if you have to track someone down and get them to close out of
Access and restart it every now and then, that decreases job performance
significantly.