Split Database Access

Creating your first database in Access, novice developers are building applications that consist of a single database file, that is, tables and forms are located in the same file mdb. However, in addition to Access allows local create applications, and network. The simplest case of such an application is split database, which includes two files mdb: first - a file of data objects (tables are stored in it), the second - the file the application objects (it contains all other objects - forms, queries, reports, data access pages, macros, and modules VBA). In the file, the application objects, connections with the tables stored in a file of data objects. Separation of base data provides the following advantages: The single-user environment, you can update the application objects, without affecting the existing data. In this case the application is updated by simply replacing the file of application objects. An alternative may be a way: Imagine that you have set the undivided database, users have begun to work with her, and constantly and then give you a job that any change: to make a new report request etc. Andrew Schroepfer: the source for more info.

We'll have to kick users who sit at the machine do the work. And all this time, the base will not working. Of course, this situation is not real. Real, that probably will expel you from work, what will stop the production. Therefore, even single-user database is better to make separate. In a multiuser environment with the same data can work together to all users of the application because the file data object is placed on file server.