>One should be sceptical of any bandwagons sent out by today's software companies. Targeting VFP at middle-tier duties is just one way to position VFP. Remember, VFP is possibly the only MS product that if it never existed, there would be no reason to invent it. I think we all need to acknowledge this fact and quit whining. You know and I know and everyone who matters at MS knows that VFP can do it all.
>

I don't like this middle-tier positioning. I think that VFP is only passable as middle-tier object. Maybe, just maybe, we should be looking at pushing VFP as a workgroup solution because, after all, not every solution is client/server. Once you remove the need for a c/s solution, VFP is almost unbeatable.

>Moreover it's highly doubtful that future enhancements, especially UI enhancements, will be made in core code. This is true of all MS products.

100% agree. Looks like MS is pushing for external ActiveX components down the road instead of intrinsic control sets. This is actually favorable for VFP developers (well...for *all* developers)....learn a control's PEMs once and apply to any situation or environment.