>>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?
>>
>Yes, I do.
>There's nothing magical about the _base classes. Do a search to determine if there are 2 copies of the class. Use the advanced Find to locate any occurrence of that class code. Look for:
>"PROCEDURE Error
>LPARAMETERS nError, cMethod, nLine"

yep, did all that. Went round renaming all Procedure Errors to Procedure Err - which finally shut the damn thing up.

but this is interesting...
>
>Once an old copy is in memory, you will get its behavior. Say you made a little developer app that does some task for you. You DO MyHelper.APP. Whatever classes that were available when the App was compiled are now in memory. If you modify those classes, then run, you may still get the older code. So even when there is no other copy of the vcx, you can still be executing its code...until you re-compile those apps.

are you saying that even if you leave the vfp environment and re-enter it, the old behaviour will still resurrect itself?

actually I did a test and it did seem to confirm that. The change in class didn't 'stick' until I recompiled...
Yet I have/do make frequent changes to classes without recompiling and without any similar problem. What causes the selectivity?


Thanks

Harry