>David -
>
>>Hey there George!
>>
>>I've never seen VFP go into "psychic predict mode *g*" when executing code I'm only on a P2-300 though. Are you sure you don't have code somwhere along the class tree that's causing this? DoDefault() can do some odd things when issued to an empty parentclass because the baseclass behavior gets executed twice. But baseclass behavior isn't going to have any effect on custom poperties or methods of an object. I'd seed a few debugout calls through your methods to track this down.
>>
>>You sure you don't have some asynchronous code like in a timer that's biting you?
>>
>Thanks for the reply. We do have some timers. I'll check them out.
>
>- George [As for the debugout's, I've tried tracing. It fixes the problem. Maybe I'll just get the users to trace every line of code...]


David,

I've run into this many a time. The infamous =inkey(.01) does wonders. I limit my use of timers to a bare minimum, I get too many headaches with those #$^%#% things especially when debugging. Its a horror. I've got a base class of a timer where I put a bit of code (if type('ISDEBUG') != 'U' .and. ISDEBUG = .T. THEN TURN OFF THE TIMER.)
Back to the inkey(.01). I've used this many a time when vfp seems to run the code of a line before the other is finished. I don't really know why this is the case, but its happened to me many a time.

Robert