Hi!

Usually I do the same too. However, the interruption of long process looks for me like the 'Cancel' command in VFP. The "return to..." here looks like the Cancel command, but it do not cancels it at all, just returns to the higher levels of the call stack. VFP is designed also to be universal to organize the long data processing, thus there are some things that are unusual for structured programming and are quite useful.

>>Hi!
>>
>>Then, if subroutines used, this approach might be even more better.
>>Take a look to the RETURN command help. As you see, you can return to any procedure from the procedures call stack missing the rest of all other procedures code that are called after the procedure where you returning to. For example:
>>
>>

>>A.pRG
>>....
>>DO B
>>    B.PRG
>>    ....
>>    DO C
>>         C.PRG
>>         ....
>>         DO D
>>              D - return to B here
>>         ... - this code not running after return from D to B
>>    .... the rest code of B
>>

>>
>>I guess you can use that way to return to special program that call the entire process from any subroutines.
>>
>>PS: I understand that certainly the thread was about other things, however, I just tried to answer your particular question about returning from the any point of the long process. As you see, you can organize this without constant checking for some logical variable. Tough this violates the OOP and structured programming, so this should have limited use.
>>
>
>Vlad,
>
>Thanks for the explanation. My original intent was to re-write code using structured programming...