BUG: Temp Environment Variable Causes Unusual Behavior in VFPLast reviewed: January 19, 1998Article ID: Q179480 |
The information in this article applies to:
SYMPTOMSAfter you attempt to start Visual FoxPro, one of the following occurs:
CAUSESetting the Temp environment variable to any two directories separated by a semicolon (;).
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATION
Steps to Reproduce BehaviorWARNING: Attempting the following steps may adversely impact some 32-bit applications and necessitate uninstalling then re-installing any affected applications. Specifically, attempting the following steps with Visual FoxPro 5.0x on a Windows NT 4.0 machine results in an abnormal start up of Visual FoxPro 5.0x after the Temp variable in the User Variables list has been reset to a solitary directory. To correct this problem, click Start, Run, and enter "C:\Program Files\Devstudio\Vfp\Vfp.exe" -A at the prompt. Visual FoxPro 5.0x may then be started normally from the Start Menu or from a shortcut. However, if this method fails, it is necessary to uninstall and re-install Visual FoxPro 5.0x.
Keywords : FxenvGeneral vfoxwin Version : WINDOWS:3.0,3.0b,5.0,5.0a Platform : WINDOWS winnt Issue type : kbbug Solution Type : kbpending |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |