Are you seeing the issue with just one method of the form, or with all methods?

If just one method, ISTR running into something like that once. It turned out there was something weird in the code stored in the .SCX/.VCX. I created a new one with a different name and copy/pasted all the PEMs to it, IIRC that fixed it. There's probably a more elegant way to do it.

You could USE the .SCX/.VCX and BROWSE it looking for anything obviously amiss.

>Hi Al,
>
>I don't think it is a timer - doesn't mess up other screens, just this one. I tried recompiling the form but that did not help - it seems as though the debugger cannot "find" the correct line to display - it's in the correct method, just that the focus is at the bottom of the message.
>
>Albert
>
>>
>>Some frameworks (such as VMP) have background timers running all the time, which seriously messes up debugging. In those cases, prior to SET STEP ON you need to issue some commands disabling those timer(s).