Hi, Jim.

>Virtually everything about this announcement says 'get your *ss over to .NET as soon as you can'. In return you will get extensibility of your VFP investment in .NET.

I beg to differ. If Microsoft were trying to force you badly to go to .NET, they could just cut any further development, and maybe let all us wait for years for another version. If they are spending at least 10 bucks to let us make better interop with .NET, it is because they are willing to let you and any other VFP developer to keep woking with FoxPro and support your customers while using their new technology.

That said, I think it is obvious to anyone that Microsoft would prefer that ANYNONE uses .NET.

Don't know about you, but my own company has three main different "generations" of our applications still running: a very old DOS suite that about 4 mid-sized customers are using (not surprisingly from goverment), then a Windows, DBF-based suite, and finally a Windows, SQL-server based, n-tiered suite. 90% of or customers, and 98% of our revenue comes from the latter version. Do you guess who are most cost-intensive for us from a support perspective?

But we keep supporting those customers, even while the older versions don't get any update, because they are our customers after all. However, of course, we don't let any chance go without recommending them to upgrade for our latest version. Maybe the solution they have is good enough for them, and maybe some old features anre not in the new versions anymore, but for us it is a matter of strategy. Can we blame us for trying to move them on? do you think tht they wont have some important benefits just from embracing our main product strategy?

Best regards,