>>>>This really translates to "we really want you to convert Visual FoxPro code to .NET, not interop with legacy code"...
>>>
>>>Realistically, I'm not sure I would expect anything else. MS is not the Ben and Jerry of software.
>>
>>Well I'd say, Jay, that this is the wrong "attitude" (for lack of a better word).
>>VFP has, at least to this point, a far far larger market (for its applications) than does .NET+SQL Server+???
>>With Linux continuing to be a "problem" for MS they have even more impetus to continue to push VFP - their only other real database application product - to keep Linux at bay.
>>
>>So MS doesn't have to be a "Ben and Gerry" altruist, it just should show that it wants to protect and grow all of its business.
>>
>>As a user of VFP shouldn't YOU be pressing MS for more publicity/exposure/growth of VFP rather than just accepting MS' all-out push of everyone towards .NET? You are the customer you know!
>>
>>cheers
>
>I'm with you on some of that. MS "should" show that it wants to protect and grow "all" of its business, but that simply is not realistic. That would be wonderfully sweet. But that's not profitable. As a developer I would not create core functionality just so my clients were able to retain their legacy code, but rather work with them to use my new technology and functionality with appropriate backwards compatibility. I do not expect anything more from Microsoft. I do have apps in the non-profit sector that I maintain because the organizations do not have the money to upgrade hardward, etc. That is a Ben and Jerry attitude. But that doesn't pay my bills, just like staying with increasingly outdated legacy code won't pay Microsoft's.

Jay,

But who are *we* to worry about MS' profitability????

*WE* should worry about ourselves before we worry about MS' profitability! And we certainly should worry about other societal factors before we worry about MS' profit. Especially with all the bucks MS has stashed in the bank!!!

MS has seen fit to pour a piss-pot full of money at .NET, to the exclusion of things its CUSTOMERS want/need! This can be fine if it results in ALL CUSTOMERS being so impressed and pleased with all the new stuff AND a nice simple painless way to convert that everyone converts en-masse.

But we aleady know that ain't in the cards!

"...work with them..." (its customers) is what they should do but when have you seen MS do that with VFP or any other product, unless you're a multi-national corporation??? MS bought FP and with it its obligations to its customer base. That MS has continued FP/VFP long since purchase in no way lets them off the hook today. MS is fully aware that there are countless production applications out there working productively for their users. MS is fully aware that most of those customers have no need/interest to have the bells and whilstles afforded by .NET.

The major point anyway is that *WE* (repeat: WE) are the CUSTOMERS and it is high time we started acting like CUSTOMERS rather than like sycophants. How we get ourselves into a position where we "champion" Microsoft and its practises is way beyond me!... Is it because they are the only game in town so we feel like we better not upset them???

cheers