>>> 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!

Any advantage to which, VFP7 or VFP8 style?

If you're looking for advantages to 7.0 the only one I can think of is if the code is already written in VFP7 and I don't feel like rewriting it, then it would be advantagous to leave it in 7.0.

Otherwise the advantage to structured exception handling (in a mouthfull) is the ability to pass complete exception information simply through nested blocks of exception code that isn't decoupled from the function code where you're expecting the exception.

That isn't possible in VFP7.