>>> Try/Catch (though EPS gave our UG a great presenattion) is for projects more sophisticated than mine.
>>
>>Not at all. Try/Catch completely replaces Error() and ON ERROR. The only reason I would consider using either Error() or ON ERROR in VFP8 is if I need to support alot of backwards compatible code. Even then I'd avoid them if possible.
>
>Any quick situation scenarios you could share to highlight an advantage would be helpful!
One DISadvantage of TRY/CATCH is that the RETRY command cannot be used there, if you need it. Technically it can be executed, but will not RETRY the code line you need.
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro
"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison