• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 22. HANDLING MULTIUSER SITUATION... > ONE OR TWO DATABASE CONTAINERS: KNOW...

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 for better performance are discussed shortly.) After splitting up a database, you have to relink the tables, which is covered in great detail in Chapter 26, “Startup Checking System Routines Using DAO,” and Chapter 27, “Startup Checking System Routines Using ADO.”


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint