SUSPEND has been in the language much longer than TRY/CATCH. This is another one of those things that frequently programmers put in, then have error code to ignore the runtime errors. Again, the VFP team is not responsible to take fix issues caused by lazy programmers.

Presentation of an Open dialog is not an error. Did you consider the possibility that someone may very well want the command to work the way it does?

>Craig,
>
>With all due respect, there are TONS of things in VFP that could be thrown out if the yardstick is elimination of "lazy programmers".
>
>In THIS case there are, in my opinion, two flaws to your logic:
>1) If TRY...CATCH is designed to catch errors, then why doesn't it catch this error?
>2) TRY...CATCH is itself the product of requests by programmers, all of whom must themselves have been very lazy when one considers that there has always been an error handling capability in Fox!
>
>Finally, I don't see in the Help entry for TRY...CATCH...FINALLY Command anything that describes what errors will or will not be caught in the TRY code. Perhaps if the documenters had seen fit to record that information it would have embarrassed the VFP Team into making it handle ALL errors!
>
>Jim