MOD2000: Changes That You Make to an Access Module After You Check It in to Visual Source Safe Are Lost (236545)
The information in this article applies to:
- Microsoft Access 2000
- Microsoft Office 2000 Developer
This article was previously published under Q236545 Advanced: Requires expert coding, interoperability, and multiuser skills.
SYMPTOMS
You can edit a Microsoft Visual Basic for Applications module after you check it in to Microsoft Visual Source Safe. However, changes that you make are not saved. Access does not warn you that your changes will be lost.
CAUSE
If you keep the Visual Basic Editor open after you check a module in to Visual Source Safe, you can make further changes to the module in the Visual Basic Editor. However, you are not making these changes to the module in Visual Source Safe because you did not check that module out again. Therefore, the changes that you make are lost.
RESOLUTION
To work around this behavior, make sure that you close the Visual Basic Editor before you check in your modules.
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/16/2004 |
---|
Keywords: | kbbug kbpending KB236545 |
---|
|