Microsoft KB Archive/163704

= ACC97: Some Access Commands Don't Prompt to Check Out VSS Module =

Article ID: 163704

Article Last Modified on 1/19/2007

-

APPLIES TO


 * Microsoft Access 97 Standard Edition
 * Microsoft Visual SourceSafe 4.0 Standard Edition
 * Microsoft Visual SourceSafe 4.0a
 * Microsoft Visual SourceSafe 5.0 Standard Edition

-



This article was previously published under Q163704



Moderate: Requires basic macro, coding, and interoperability skills.



SYMPTOMS
When you open a module from the Debug window, from the Object Browser, or with the Find or Replace commands on the Edit menu, Microsoft Access does not prompt you to check out the module, and you cannot save your changes.

This article assumes that you are familiar with using the client-side capabilities of Visual SourceSafe. For more information about Visual SourceSafe, please refer to the "Visual SourceSafe User's Guide" or the Help topics available from the Visual SourceSafe Help menu.



RESOLUTION
Check out any object in your database before you make changes to it.



STATUS
Microsoft 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.



Steps to Reproduce Behavior
 Create a new database and add it to Microsoft Visual SourceSafe.  Create a module and type the following procedure: Function NoCheckOut Msgbox "Hello" End Function  Save the module as VSSTest and add it to SourceSafe. Press CTRL+G to open the Debug window. In the Debug window, type NoCheckOut, and then press SHIFT+F2. The VSSTest module opens in Design view, but Microsoft Access does not prompt you to check it out.</li> Type the following comment in the module: ' This is a test.</li> Note that the Save icon on the toolbar and the Save command on the File menu are both dimmed. Close the module and note that you are not prompted to save it.</li> Open VSSTest in Design view. Whether you check it out or not when prompted, your changes are not there.</li></ol>

The same behavior is exhibited if you open a module from the Object Browser, or if you use the Find or Replace commands on the Edit menu.

<div class="references_section">