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

Chapter 19. Linking Access Front-Ends to... > Creating Multiuser Access Applicatio...

Creating Multiuser Access Applications by Linking Tables

A single .mdb file that contains Access application objects (forms, reports, macros, and VBA code modules) and Jet data objects (tables and queries) is one of Access’s strongest selling points. Other desktop database management applications—such as Visual FoxPro and Visual Basic—require multiple files for a single database application. The obvious advantage of a single .mdb file for a complete Access application is simplicity. You can deploy your application by copying its .mdb file to another computer that has Access 2003 installed.

Sharing your Access application with other users in a Windows XP workgroup or Windows 2000/2003 Server domain requires separating the application objects from database objects. It’s theoretically possible for multiple users to simultaneously share a single .mdb application on a network or use Windows 2000+ Server’s Terminal Services to run multiple instances of the application. In practice, however, application response time and network traffic issues make the single .mdb approach impractical for all but the simplest database projects. Another disadvantage of the single .mdb approach is that making changes to any Access object by opening it in Design mode prevents other users from using the object.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


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