Demetrius:

There is no way for another to answer your question
responsibly - there is too much data required - and in the
final analysis, you have to live with the decision.

This was a tough question before the very annoying rumour
about MS dumping VFP. As a consultant, I must answer the
question for my clients. Just when I recommended the move to
VFP for the one client I have with legitimate need for OOP
and the client-server upgrade represented by VFP, the rumor
hit the fan.

I suggest you invest a week. Read Flash's CodeBook 3, (or
some other book) which goes into the issues of OOP. Take a
look at the foundation provided, but use it only as an
abstract. (Some parts can be used as-is, but you will be
re-writing much.) If you have the resources, do one of
Flash's Road Shows. I recommend the book and show, but not
the rote use of the code. I know of too many people who got
into a hole this way.

If you need client-server, and can benefit from the OOP
paradigm, transaction processing, referential integrety,
etc., it really means you have enterprise systems of some
magnitude - otherwise there is little benefit to the OOP,
foundation and classes.

Finally, you need a crystal ball to offset the concern of
MS dumping VFP. Their recent overtures, and announcement
of a DevCon help, but it is still a stigma. My guess is
that most folks who are sitting on the fence will move over
to VFP when they can, just to stay contemporary.

Put off the decision! Wait and see. 2.6 is strong. You have
read the CIS threads from programmers who are having a tough
time with VFP?

Best,
Randy