PRB: Saving a File in FrontPage Does a Silent Check In (183735)
The information in this article applies to:
- Microsoft Visual SourceSafe for Windows 5.0
- Microsoft Visual SourceSafe for Windows 6.0
- Microsoft FrontPage 97 for Windows
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:
- Always check files out before editing them.
- 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.
- 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.
REFERENCES
For additional information, please see the FrontPage Server Extensions
ResourceKit at the following Web site:
Select Administration Tasks and Procedures, then Microsoft Visual
SourceSafe 5.0 Integration
For additional information, please see the following article in the
Microsoft Knowledge Base:
171116
HOW TO: Enable VSS Integration With FrontPage and Visual Interdev
(c) Microsoft Corporation 1998, All Rights Reserved. Contributions by David de Groot, Microsoft Corporation.
Modification Type: | Minor | Last Reviewed: | 3/21/2005 |
---|
Keywords: | kbinterop kbprb KB183735 |
---|
|