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

Chapter 18. A Strategy to Developing Acc... > Splitting Databases into Tables and ...

Splitting Databases into Tables and Other Objects

When earlier versions of Access ran in a multiuser environment, it was imperative that you place the system's tables in one database and the rest of the system objects in another database. With Access 95 and the advent of replication, you could either split the tables from the other objects or use replication to deploy design changes without compromising live data. Access 2000, Access 2002, and Access 2003 take this a step further with the Access Data Project (ADP), in which Access stores tables, views, stored procedures, and data diagrams in a SQL Server database or the SQL Server 2000 Desktop Engine (formerly the Microsoft Database Engine, or MSDE). Access stores forms, reports, macros, and modules in the ADP file.

Despite advances in the later versions of Access, splitting tables from other system objects is a very viable solution. For simplicity, I'll refer to the database containing the tables as the Table database and the database with the other objects as the Application database. Linking from the Application database to the Table database connects the two databases. This strategy enhances


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


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