>>>>>
>>>>>There just doesn't appear to be room for more than one grand vision in the Developer Division at MS. Anything that is not .Net oriented is not really given much thought.
>>>>
>>>>Now that's a shame...
>>>>
>>>>>
>>>>>It's not about fulfilling a need, it's ignoring a need that isn't going anywhere soon. Look at the popularity of non-MS tools like FileMaker.
>>>>
>>>>True. It's the old "one-sized hammer no matter what size the nail is" -syndrome. FileMaker is great for what it is, but it ain't no Foxpro -- the scripting language is hideous. I can't think of anything else that comes even close to VFP, for what IT is -- small-footprint, easy-and-free-to-distribute, end-to-end AND expandable development environment with a nice OO model. What a waste, indeed, letting it wither on the vine...
>>>>
>>>
>>>I agree with all your points. But if Microsoft were to continue developing VFP, what features would they add? A better menu builder? Others have said VFP is more or less feature complete and I tend to agree.
>>>
>>>The floor is open -- what would anyone like to see in VFP that isn't there now?
>>
>>Mike, don't be so naive. New development means that MS will continue to fix bugs caused by new OS/hardware, and 3rd party vendors will continue to test their products for VFP.
>
>
>Edward, don't be so cynical. Microsoft has said they will fix show stopper bugs caused by future Windows releases during the support time horizon.
>
>Will we be unscathed? Probably not. VFP apps may run without crashing but seem increasingly out of date. All I can say is we have 3-5 years (IMO) to be agile little frogs and jump to other pads.

Being semi-retired I hope to avoid amphibian future.