FrontPage Checks Out the Wrong Version of a Pinned File in Visual SourceSafe

When you pin a version (other than the latest version) of a file in Visual SourceSafe, FrontPage and Visual InterDev check out the latest version of the file and do not adhere to the pinned status of the file. You can also save new revisions of the file.

Pinning does not work correctly with Web content that is developed by FrontPage or Visual InterDev. The OLE Automation that the FrontPage Server Extensions use to connect to the Visual SourceSafe database does not support that feature. However, Visual SourceSafe still lets you check out a version other than the one that's pinned.

Microsoft has confirmed that this is a problem in Visual SourceSafe.

Pinning is used to declare an earlier version of a file as the latest version and lock changes to that file. When you use pinning, you can designate version 3 of a file as the latest (pinned) version, and even though there may be later versions than version 3, version 3 will be used. FrontPage does not have an interface for controlling pinning. Files can be pinned using the Visual SourceSafe Explorer history features.

For more information on pinning and Visual SourceSafe, please see the Help file for Visual SourceSafe.

To resolve this problem, obtain the latest service pack for Visual SourceSafe. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: