John,

Ignore this Karls guy. He is just getting a kick taunting us and lauging at our fear that MS will indeed succed in phasing out FP for VB.

Naturally we like FP. It is really a very well designed language, and we are familiar with it.

As far as Jim Nelson's complaint that VFP is not addressing the real user needs; that is partially true, but stability in a language is also a plus. Consider COBOL, and by comparison consider how many Fox developers did not move to VFP 3.0 from FP 2.6. Graduallity and digestion are important factors.

While you are at it, look up also www.devx.com >> Magazines|VBPJ >> Table of contents >> Guest Opinion by Ash Rofail. Although Rofail goes to great pains to not blame MS for new features, he points out that a constantly changing language is hell on developers.

A personal opinion: for the time being I am more interested in learning what is already available than in many new things. To me the most important addition to VFP would be a better automated tool for migrating FP 2.6 apps to VFP. Something along the lines of MEI's migration methodology, but more automated. I would pay $$$ for that.

Keep cool,

Alex