I am glad to hear that you have been giving Fox a shot and your comments are always welcome. I am also happy the therapy is paying off and you are no longer emotionally tied to the tool(s) you use to make a living. As you can see I haven't quite progressed that far.

I also agree with much of what you said particularly the part about M$ not supporting FoxPro very well. That in a nutshell is what I am griping about.

I have grown tired of M$ trying to pigeon hole FoxPro to some less than
glamorous n-tier development tool only because they have not been able
to squash the product through leaked demise rumors, un-informed or under-informed sales people, and almost no marketing/advertising (or worse negative marketing).

The truth is FoxPro is a very good tool, well versed for many situations, excels
in data manipulation/handling, and has reasonable OOP capabilities. I could
use ActiveX controls written in C with a VB front-end going against SQL Server
data but WHY invest the effort and money when I can often times provide the
same solution with one $300 dollar product in less time.

I agree that one tool cannot 100% of the time be the only solution for every
situation and I think the there is value in the Visual Studio/Suite approach to
development. However, I disagree that I should be using (and charging clients/employers for) two or three different tools, that require considerable more effort to get the job done just so M$ makes more money. This is what will happen in many instances when data-centric tools like FoxPro are gone....

I have little interest in using a low level tool like 'C' and have no experience
with Delphi so I can't comment on how much better a tool it may be over VFP. I
primarily use VFP and VB but have been giving JBuilder some thought should I make a change in the near future.