>>Sad to say that VFP is not going to be part of CLR and MSIL.
>
>At first, I was too. Now, I'm not so sure.
>
>.NET is an aggresive strategy which could possibly not succeed with respect to CLR. Alot of hurdles will have to be overcome before it's acceptance as a mainstream development platform.
>
>Time will tell - two to three years.

That should be long enough to decide what my next development language will be. Let's see.... Oz? Smalltalk? Forth? RPG-II? I know! Cobol!!!!

This is a funny industry... Intel, who should've dropped 8080 (real mode) compatibility long ago, maintains it. MS, who should strive for backward compatibility does the opposite!

This CLR thing... 2-3 years... Considering the timeframe I betcha MS is banking on a 4GHz CPU on every desk with 16GB of RAM and a 2.3TB Hard disk. Of course, Office 2002 (2004 won't be released until 2006) will probably take 1.5TB of hard disk and won't run acceptably fast until you upgrade to 32Gigs of RAM and a 6.5GHz cpu.

;-) Alex