Article ID: 195025
Article Last Modified on 10/15/2002
APPLIES TO
- Microsoft Visual SourceSafe 6.0 Standard Edition
- Microsoft Visual FoxPro 5.0 Standard Edition
This article was previously published under Q195025
SYMPTOMS
When you try to check in a .prg file into Visual SourceSafe that contains Visual SourceSafe keywords, you might get the following error:
CAUSE
This bug has only been seen when using Visual FoxPro 5.0 with Visual SourceSafe 6.0.
RESOLUTION
Make sure that you have compatible versions of Visual SourceSafe and Visual FoxPro. This problem can't be duplicated in Visual FoxPro 5.0 and Visual SourceSafe 5.0 or Visual FoxPro 6.0 and Visual SourceSafe 6.0.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.
MORE INFORMATION
If Keyword Expansion is enabled and the .prg file contains a keyword, Visual FoxPro generates the error while doing a check in.
Steps to Reproduce Behavior
- Open Visual SourceSafe 6.0 Administrator.
- Under the Tools menu, click Options, and then click the General tab in the Options dialog box.
- Add *.prg in the list of "Expand keywords in files of type:" text box if it is not there.
- Close Visual SourceSafe Administrator.
- Open Visual FoxPro 5.0. and create a new blank project, Proj1, and save it under C:\proj1.
- Save the .prg file as Program1.prg under C:\Proj1.
- Add the project to Visual SourceSafe under $/proj1 and update the project list.
NOTE: The padlock glyph will indicate that the .prg file is added to Visual SourceSafe. - Check out Program1.prg.
Modify Program1.prg and add the following lines:
* $History: $- Save and check in Program1.prg.
RESULT: The following error message appears:
REFERENCES
141504 HOWTO: Make SourceSafe Keyword Expansion Work in Text Docs
Keywords: kberrmsg kbbug kbnofix kbinterop KB195025
