I agree 100%. I am hoping that VFP stays out of the CLR debacle because when it all crashes and burns next year (lol) VFP will emerge pristine :-)
OTOH, someone (maybe Calvin?) in Miami mentioned a MUCH more intriguing idea, and that is a WinCE version of VFP. Even if you have to remove backwards compatibity with FP and maybe DB events and stored procs, I think that would kick ass.
>If we could have both, IOW, VFP continues along the same course it's been on since MS got their hands on it (from a technical standpoint) and we got VFP.NET which was a CLR version of VFP that just supported what the CLR can handle, then that would be interesting. Unfortunately, if we got VFP.NET, I think development of regular VFP would stop just like it has for VB.
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05