>Nonetheless, if you have a solid business model and you are using Fox - and you have a good customer base who does not care about technology specifics - then I believe one can stay in Fox for some time to come.
>

I think a lot of developers seem to miss this point anytime a "VFP is dead" thread comes up. I >like< using VFP, and will use it anytime and as long as it makes sense; from what I can tell, I'll be doing VFP coding for quite a while yet (at least another 3 years, which is forever in computer terms). I also like ASP.NET and C# and I'm looking forward to the enhancements in Whidbey (Windows Forms are still pretty weak in my opinion). Some of the new things in Europa should be pretty cool too.

The architectual changes coming around for Longhorn may not fit with VFP as it is today. From what I've seen, it would probably take a significant amount of effort to make it an equal partner with the current (and future) .NET tools. I don't think Microsoft will (or can) justify the amount of effort it would require to make it work (even if they could justify the "why"). So, yeah, in some respects, I'm seeing the end of the line for future VFP development, which makes me a little sad. But it's also quite a few years off, and if I really wanted to, I could keep using it for a lot longer. But I can imagine that I won't want to - just like I don't like working on old 2.6/DOS (or even Windows) apps.