Microsoft KB Archive/183735

= PRB: Saving a File in FrontPage Does a Silent Check In =

Article ID: 183735

Article Last Modified on 3/21/2005

-

APPLIES TO


 * Microsoft Visual SourceSafe 5.0 Standard Edition
 * Microsoft Visual SourceSafe 6.0 Standard Edition
 * Microsoft FrontPage 97 Standard Edition

-



This article was previously published under Q183735



SYMPTOMS
When you open a Source Controlled file for editing in FrontPage, and respond "No" when prompted to check it out, saving the file checks in any changes that were made.



RESOLUTION
Depending on your working environment, consider the following options:


 * 1) Always check files out before editing them.
 * 2) After opening the file, save it to a different location before editing the file. NOTE: There is no way to automatically enforce either of these options.
 * 3) If a file has been inadvertently checked in, you can use the SourceSafe Explorer to rollback to an earlier version. After doing a rollback, users also have to select 'Recalculate Hyperlinks' to get that rolled- back version out of the Visual SourceSafe (VSS) database into their master Web. Otherwise, the master Web version will still be what was last saved.



STATUS
This behavior is by design. When you save the file, FrontPage performs an implicit checkout - update [ASCII 150] checkin, in order to keep the version in the SourceSafe database synchronized with the content on the Web.



Steps to Reproduce Behavior

 * 1) Using the FrontPage Explorer, open a Source Controlled Web.
 * 2) Open a file that is currently checked in, and select "No" when prompted to check it out.
 * 3) Edit the file and save the changes.
 * 4) Using the SourceSafe Explorer, show the history of the file, and note that a new version was created when the file was saved.

NOTE: The exact behavior depends on the version of the FrontPage Server Extensions installed. In certain versions, messages such as "The file has been automatically checked out" are displayed, in others, no notification is given.

