By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,610 Members | 1,957 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,610 IT Pros & Developers. It's quick & easy.

Network Performance

P: n/a
I would like to know a little bit more about how Access works over a
network. My situation is:

A split database with the program .mdb installed on the workstation
and the backend .mdb on the server.

One question I have is, if the backend .mdb contains 3 tables, and the
program on the workstation uses table 1, what travels across the
network ? Only table 1, or the whole .mdb ? Would 3 separate backend
databases be better ? Or worse ? For example, instead of tables 1,2
and 3 located in _be.mdb, 3 separate *_be.mdb files with one table in
each file. Thanks you for any help or insights regarding this.

Apr 9 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Access uses a Jet backend the same as it would use the .MDB tables and data
file on a local hard drive... that's why it is called a "file server"
database.

Only that information necessary for the operation at hand will come across
the network, though all manipulation and extraction is performed on the
user's machine. If you have provided a criteria for an indexed field (not
limited to the Primary Key), only the index will be brought across the
network for the initial comparison, then only the specific records that meet
the criteria will be brought across. So if you are very specific in letting
the Jet database engine know what you want to see, you may only have to
bring across the network much less than even one whole table.

No, separate back-ends based on the number of tables would be unlikely to
improve performance measurably.

Larry Linson
Microsoft Access MVP
Apr 9 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.