The remaining items on the wishlist come to mind. :o) Well, you did ask! :o)

Actually, VFP is robust and mature. It is NOT perfect though. My greatest concerns are:

1. Perception of potential customers (current customers should already be sold)
2. Ability to run on new MSFT OS versions
3. Add new controls and features to meet new OS version design standards (remember when theme support was added? Who knows what's coming down the pipe)




>>>
>>>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?