Marc,

Your points are well taken, but they aren't the same as what I am getting at.

The work I have been doing in VFP for the last 2 - 3 years has been in the area of frameowrks, lately in designing an N-Tier appraoch to app development. I have not been using the UI features of the product except in providing a mehtod of defining the business rules that the business class will enforce. My work essentially doesn't care what is used for the front end or backend.

In this scenario, I ahve found the local data engine in VFP to be irreplacable for storing and processing the rules. The OO featues of VFP have been a dream to use in building sophisticated business class libraries.

I really think this is an issue of change. Over time things change and no one likes that, folks, by nautre, want thing to stay the same. Time marches on, and we have to go with the times or be lost in the dust.

My personal feeling are that I would rather be ale to continue using VFP and its rich oject and container models than watch it go the way of the dinosaur simply because it didn't keep up with the times. Being a "one tool does all" product is not keeping up with the times.