Agreed 100% Stephane.

But because it does not, the VFP Help should at least list those that it does not intercept, right in the TRY...CATCH...FINALLY topic itself! (maybe they were too lazy to find out for themselves < s >)

cheers

>Jim,
>
>I don't understand why some argue about this! This case is cristal clear, it has nothing to do with coding technique. try-catch should catch ALL Errors not just some.
>
>
>>That's damned harsh, David!
>>
>>How, in my code, could I protect against the following eventuality by other than a TRY...CATCH...: the table exists and is in fine shape and the programming reference to it is correct BUT a networking problem occurs JUST AT the begin execution of Fabio's SELECT *...? The network problem could be as simple as some collisions on a hub or loss of power on a hub or the system admin farting around and screwing up or..... What good does the Open dialogue do in that case, especially when it won't even name the table it's trying to open???
>>Meanwhile, in a TRY...CATCH, *I* can have some control and *I* can make a more informational message to the user.
>>
>>Jim