Hi Fabio,

The VFP TRY...CATCH...FINALLY structure is modeled after similar structure in other languages like Java, C#, C++. Neither of them supports retry option so there is no conspiracy on the VFP team part to deprive you of this feature. :)
Feel free to add your request to VFP Wish List.


>Hi,
>
>new TRY...CATCH…FINALLY structured handling errors is much powerful one,
>but it have a big limit:
>
>on CATCH block code i cannot use RETRY.
>
>Then if the error is correctable on CATCH code, i cannot restart
>the program on the procedure line ( at CATCH program stack level ) where the
>error fired the catch event.
>
>Classic Example is for VFP INDEX ERROR.
>
>I have found a simple solutions with ON ERROR or this.Error() and RETRY
>command ( the index is correct and the program restart on the program line
>like without errors occurs ).
>
>With TRY...CATCH…FINALLY this solution is impossible.
>
>Then i cannot implement a unique structured handling errors,
>but i need mixed global ON ERROR, this.Error() and TRY...CATCH…FINALLY.
>
>Why VFPT put this limit ! ( i don't put ? on this question )