Actually an argument could be made for porting all the VFP features which are superior to VB into VB. Then you could devote the entire VFP team plus the entire VB team to constantly improving the new VFP/VB language. The hard part in this would be to do this without ending up with a clunker that was worse than either VB or VFP. I think in adding object orientation to VB Microsoft is already taking the first step towards doing this.

>>Hi John,
>>
>>I think it's obvious that the FoxTeam needs to start feature planning for the next version fairly soon, setting budgets, etc.
>>
>>The problem with the .NET issue is that a decision will probably have to be reached while the verdict is still out.
>>
>>>I'm not entirely convinced we are talking "post-7". Robert, Calvin, and the rest seemed entirely sincere about getting feedback from everyone, not just the top x%.
>
>
>You're late. I saw Randy Brown's session last October in Las Vegas where he had his explorer open and there were several folders vfp6, vfp7 and vfp8. I raised my hand and asked him to show us what was in the folder. He laughed and quickly killed that window. They've been planning 8 for quite some time. Having said that, there's no time like right now to start telling them what we want.