PRB: Problem Adding Objects Created in VBA to SourceSafeLast reviewed: March 28, 1997Article ID: Q159690 |
The information in this article applies to:
SYMPTOMSModerate: Requires basic macro, coding, and interoperability skills. If you are developing a database application that is under Source Code Control (SCC) using Microsoft Visual SourceSafe integration, and you create a database object programmatically using Visual Basic for Applications code, you are not prompted to add the new object to SCC control. When you try to add the new object manually, you receive a message that there are no objects to add to Visual SourceSafe.
CAUSEWhen you create the new object programmatically, Microsoft Access 97 fails to notify the SCC integration that a new object exists. This causes a situation where you cannot add the new object to SCC control until you close and reopen the database.
RESOLUTIONClose and reopen the database after you create new objects programmatically under Source Code Control (SCC). This allows the new objects to be added to SCC correctly.
STATUSMicrosoft has confirmed this to be a problem in Microsoft Access 97. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATION
Steps to Reproduce BehaviorTo demonstrate the issue and how it affects a form that you create programmatically, follow these steps. NOTE: The steps in this example require you to install Microsoft Visual SourceSafe.
|
Additional query words: SCC ACCSCC
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |