Charlie..

You have brought up an interesting point about my post - so interesting that for this 1 case, I will lift my self-imposed exile from the VFP forum...

I draw a distinction between "devote time" and "use". Yes, I will "use" VFP whenever it makes sense to. I will not however "devote time" to the product. In other words, I won't spend time on figuring out ways to optimize something that I believe has a limited/declining market and a limited future.

Quite frankly, I don't see my attitude toward the product to be any different than MS. i.e., if MS chooses to not make significant investments in the product, why should I?

Case and point: I had a book deal contract (major publisher) in hand to write an advanced developers book. I did not think the prevailing environment justified the investment relative to the return. i.e., it would have been a losing proposition in a market where I don't have the need or desire to sustain a loss for some future benefit - especially when the future benefit will not materialize...

If you care to discuss the merits of VFP vs ADO .NET in your environment, start a discussion over on the .NET forum, I'll be there...



>>>I have a choice - devote time to VFP which has seen far more days than it has ahead of it or devote time to VS .NET - which I think has a promising future.
>
>Why not use both? I'm doing so by substituting VFP for ADO.NET. This way I can use VFP for data intensive Web Services and VS.NET for everything else. I'm working on a project right now using this framework and really feel I'm leveraging the best of both products.
>
>Charlie