About saving design changes to a shared Access database (MDB)

If you don't have exclusive access to an Access database, Access will alert you when you might not be able to save the following major design changes:

• Changes to database objects (except table and queries) made in Design view
• Changes to a form property sheet in Form view
• Compiling the project, modifying project properties, or adding or removing a reference in the Visual Basic Editor
• Renaming, pasting, or deleting a database object
• Saving a database object as another type of database object
• Adding or modifying controls on a command bar
• Editing custom groups in the Database window
• Creating, renaming, moving, and deleting a data access page

If you don't have exclusive access to an Access database, Access doesn't alert you when you might not be able to save the following minor design changes:

• Changes to datasheet formatting properties, such as line styles and fonts
• Freezing, unfreezing, hiding, and showing datasheet columns
• Adjusting datasheet column width and row size
• Changes to the filter or sort order for a form or datasheet
• Changes to the state of a subdatasheet (whether expanded or collapsed)
• Changes to the OLE/DDE link of an OLE object or changes to the contents of an unbound object frame
• Changes to printer settings
• Changes to a command bar, such as its location and whether or not it's visible
• Changes to the layout of the Database window

If you are going to share the design of an Access database, consider using the following strategies:

• Assign specific objects or groups of objects to specific developers. For example, assign one developer to design forms and another to designs reports. Then, each developer can work on a private copy of the Access database. When your development team is ready for testing, assembly, and production, each developer can export the database objects from their private copy of the database to a main Access database.
• Use a source code control program. If you use Visual SourceSafe, it's a good idea to run the Performance Analyzer (on the Tools menu, point to Analyze, and then click Performance) on a regular basis to maintain optimum performance.

• If another user has a table open or is viewing data in queries, forms, or reports based on the table, you can't make any changes to the table's design. Microsoft Access informs you that it is read-only.
• If objects are dependent on one another, update all of them at the same time so that other users don't open inconsistent versions of the objects. For example, if you want to add fields to a form, make sure to add the fields to the underlying query before you update the form.
• If you change a query that another user has open, that user must close and reopen the changed object to use the latest version. With Microsoft Visual Basic for Applications (VBA) modules, other users can't run the updated Function or Sub procedures until they close and reopen the Access database.