John

I agree, everything changes. IMHO:

In the Windows sandpit: in 3 years, Longhorn will usher in a new way of developing where a modified XML string can be an application while Avalon promotes managed code apps whose underlying framework is part of the OS. I.e. no colossal dotNET download before you can do anything.

As Borland says, "the language wars are over. The Developers have won". The "point" is that developers can use their favourite tool to create managed code, while teams can pick and choose different tools whose IL output will form a seamless app.

But not VFP, because MS has already said that VFP will not be a player in this brave new world. 3 years is a long time, and there is no guarantee that all of our customers will obey the OS upgrade siren, but the timeframe is there.

In the Linux sandpit: VFP can play, but Kylix, PHP and the like are better known and at the end of the day, they are a far more realistic option even if the current VFP license limitation hurdle is overcome.

In the Mac sandpit: VFP is hardly an option at all, as far as I can tell..

What to do? Sure we all need to be watching and learning and getting ready for change, while we "stay productive" today. VFP has actually done really well for so long without the major upheavals that characterised many other tools, and VFP still has a lot of life left in it. Its survival is a tribute to the product, the community and to MS which, when you review progress since 1995, has really grown VFP and kept it technically relevant until dotNET when the gurus all said that VFP should not join in.

While you look at various dotNET options - and C# and VB.NET are certainly not the only options- make sure you also check out Kylix which will allow you to develop for multiple camps and deliver apps to almost any customer, no matter what else happens or does not happen with the OS.

Regards

j.R