MOD2000: Changes to Access Database Are Saved Without .ACB Checked Out (234823)
The information in this article applies to:
- Microsoft Office 2000 Developer
- Microsoft Access 2000
- Microsoft Visual SourceSafe for Windows 6.0
This article was previously published under Q234823 Moderate: Requires basic macro, coding, and interoperability skills.
This article applies to a Microsoft Access database (.mdb) and to a Microsoft Access project (.adp).
SYMPTOMS
If you do not check out Data and Misc. Objects (*.acb) from source code control before you make changes to the project properties of your database, your changes are saved locally but you are not able to check them into source code control. When Data and Misc. Objects is checked out at a future time, the local changes are overwritten.
CAUSE
Changes to VBA project properties should not be saved at all unless Data and Misc. Objects is checked out. However, the VBA Source Code Control Integration Add-in allows these modifications to be saved locally. There is no way to check these changes into source code control unless you check out Data and Misc. Objects and make the changes again.
RESOLUTION
Check out objects in your database before you make modifications that you intend to save. Always check out Data and Misc. Objects before you make changes to the project properties of your database.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
Modification Type: | Minor | Last Reviewed: | 7/14/2004 |
---|
Keywords: | kbbug kbpending KB234823 |
---|
|