Hi, Hilmer-

>... And code outside the TRY construct is not always executed. Although I still don't completely understand the reason.

It is not executed only when there is an error in the try block. It's not executed just means the method doesn't continue executing after the error (except, of course, for the finally).

The reason? I guess that "catch" implies to FoxPro developers that we have a chance to catch and deal with the error and then continue on if we can fix it. Is that part of the problem, do you think?

Writing that I realize that was my interpretation, too, when I first saw a Try/Catch.