Microsoft KB Archive/250495
Article ID: 250495
Article Last Modified on 1/19/2000
- Microsoft Visual FoxPro 5.0 Standard Edition
- Microsoft Visual FoxPro 5.0a
- Microsoft Visual FoxPro 6.0 Professional Edition
This article was previously published under Q250495
When using the SAVE SCREEN TO <memory variable> command, the memory variable might not be created. When using the RESTORE SCREEN FROM <memory variable> command, you receive the error:
If the screen has been CLEARed, Microsoft Visual FoxPro is not able to save anything to the memory variable, so it is not created. If the memory variable already exists, the information in it is not overwritten.
Output of some kind to the screen (Visual FoxPro Desktop) enables the SAVE SCREEN TO command to create the memory variable. The statement:
right after the CLEAR command places a null string on the screen and does not affect screen appearance, but it causes the SAVE SCREEN TO command to create the memory variable.
This problem does not occur in Visual FoxPro 3.0b.
Steps to Reproduce Behavior
Create a program in Visual FoxPro and add the following statements:
CLEAR ALL CLEAR * ? SPACE(0) SAVE SCREEN TO X ? VERSION() RESTORE SCREEN FROM X ? TYPE("X")
- Run the code and note that the error mentioned in the "Symptoms" section appears.
Remove the asterisk from the line:
and execute the code again.
Keywords: kbxbase kbprb kbpending KB250495