Harry,

The problems you have reported lately suggest something is still going on with your environment. We have something that clearly requires an exorcist, as things really should not be able to happen, but what to do we exorcise? Could there be more trouble in your environment?


>anyone remember a few weeks back I was having a problem with debugging a form because errors kept firing the form's error code and so the debugger wouldn't stop at the actual error?
>
>I'm using a subclassed library based on vfp's FCC '_base.vcx'
>
>We went through all the 'on error' business, and various workrounds but in the end, the solution was to remove the error code from the form base class. Which I did and it was fine for the next few days. I've not been back to that form till last night. And the error code has reinstated itself!
>
>Irritating, I thought, but nothing serious. Just remove it again. But this time it won't let me!!
>
>If I try to leave the error method empty, it promptly refills it. Only if I replace it with some text (even a '*') will the error code stay absent, but this doesn't disable the form's inclination to run the error method because its not truly empty!
>
>I've even 'used' the class library, found the form entry and removed the 'procedure error' from the methods field, not just from the form class but from the various other object classes that have error methods. Doesn't seem to bat an eyelid - the error method reinstates and fires itself regardless. (although it doesn't reappear in the vcx)
>
>
>
>I'm considering calling in an exorcist unless someone has a better idea!
>
>Harry