Olaf Doschke
Programmer
Help says: "Record your recent actions while using Visual FoxPro and then call Microsoft Support"
Many observations of this error conclude it goes away after a reboot:
I can confirm that, I had this error permanently yesterday, when editing a class (in a VCX). I thought it was due to compilation problems, as I have the "compile before save option" set, indeed I hadn't. I also suspected a problem due to defining a constant with an expression using another constant, but that can't be the problem due to the compile before save being inactive, too. The phenomeon went as far as a single added space caused this error, so I simply wasn't able to save any change to the VCX/VCT files. Seems the file system was confused. It's a share I created and mapped as a drive to emulate a drive I had before with that content. Also the VCX/VCT file was in source control (TFS Server), but was checked out. The editor was also not Read Only, so that wasn't the problem.
So Tip1: if you ever come across this, try a reboot. Don't investigate any further, simply reboot. One of the cases the IT crowd is simply correct.
Tip2: If all else fails, C:\Windows\System32\psr.exe is a nice tool recording steps you do as a series of pictures with side informations. In regard of "Record your recent actions while using Visual FoxPro" that could really be helpful, not only for error 1103, also for your customers reporting bugs/problems.
Bye, Olaf.
Many observations of this error conclude it goes away after a reboot:
I can confirm that, I had this error permanently yesterday, when editing a class (in a VCX). I thought it was due to compilation problems, as I have the "compile before save option" set, indeed I hadn't. I also suspected a problem due to defining a constant with an expression using another constant, but that can't be the problem due to the compile before save being inactive, too. The phenomeon went as far as a single added space caused this error, so I simply wasn't able to save any change to the VCX/VCT files. Seems the file system was confused. It's a share I created and mapped as a drive to emulate a drive I had before with that content. Also the VCX/VCT file was in source control (TFS Server), but was checked out. The editor was also not Read Only, so that wasn't the problem.
So Tip1: if you ever come across this, try a reboot. Don't investigate any further, simply reboot. One of the cases the IT crowd is simply correct.
Tip2: If all else fails, C:\Windows\System32\psr.exe is a nice tool recording steps you do as a series of pictures with side informations. In regard of "Record your recent actions while using Visual FoxPro" that could really be helpful, not only for error 1103, also for your customers reporting bugs/problems.
Bye, Olaf.