>
>Is there something similar around for VFP?

I attended the VFP Conference in Minnesota last week
and sat through a seminar on just this topic. It was
supposed to be taught by Pat Adams, but was changed at
the last minute to Mack Rubel. He knows his stuff when it
comes to VFP and FP 2.X. He taught that because of
the OOP phylosophy all object should check for
errors that they can control or pertain to them, if the
object cannot handle the error then the error method passes
control up the object hierarchy to the parent. Thus if the
parent cannot handle the error then control is passsed up
again until it reaches the form which either handles it or
gets the user out of the condition gracefully.

To invoke this concept all objects that microsoft gives you
(COMMAND buttons, LIST boxes, etc..) should all be
sub classed to a library of your choice and then you will have
the capability to add any probperty/method you require as
well as setting all of your initial error routines in all the bases
classes of the objects.

He made a good point that VFP gives the programmer the
opportunity to gaze out a window and appear to do nothing,
but in reality be thinking about how to approach problems
like ERROR HANDLING and such in an Object Oriented
way. 80% of VFP applications is thinking ahead and getting
your OOP in order.