ONE OR TWO DATABASE CONTAINERS: KNOWING WHERE TO PUT THE PIECES
When first starting with Access, most developers create a single database for all the objects used with Access. This is very convenient because you have to update only one file when updating a system. This works great when it's a single-user system. For most multiuser systems, however, this isn't so great. Performance takes a big hit when you have all your applications out on the network.
Knowing What Should Go Where: An Overview
When working with a purely Jet environment, the ideal way to arrange your system when working on a network is to have your application components—queries, forms, reports, macros, and modules—in a local database. (Other components that you can keep locally ...
Get F. Scott Barker's Microsoft® Access 2000 Power Programming now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
