Actually, the problem occurs when you use the debugger as well, which means that it's not interfering (or at least that's what I gather from the results).

The debugger also enters the infinite loop, but in it, you at least have the option to exit from it by stopping execution. In the ide, there's nothing to do other than ctrl-alt-del and terminate vfp.

Alex


>Personally I have not had time to inquire on the operation of the VM's PC (program counter) of VFP.
>
>From the first moment, it seems that TRY it creates a nested PC,
>ENDTRY update the previous level PC(-1) with the length of the try/endtry block.
>Because ENDTRY is not found, it does not update PC(-1), and the VM continue the execution
>with the PC value that point to TRY command, then the loop infinite happen.
>
>The mechanism could be various, but sure a PC remains static.
>
>The DEBUGGER it interferes with this mechanism.
>In fact the Debugger of VFP is not a probe external debugger,
>but it is part of the VM;
>therefore the fact that a program functions correctly
>in the debugger does not guarantee that functions to runtime.
>
>Fabio