Jerry,

Easier to port a less functional product to a more functional product than vice versa. I would think that VB 'cut and paste' logic would port quite well to VFP. By port I mean, mechanically translate. I understand that the resulting code would not be optimium by VFP standards.

Regards,
Malcolm


>>Hilmar,
>>
>>Now that there's a big chasm between VB and VB.NET, I believe there's a window of opportunity for Ken Levy and team to sweep in and pick up a lot of frustrated VB developers that might otherwise move to non-MS products.
>>
>>A VB to VFP translator might be a start. From a conversion standpoint, any such product couldn't possibly be worse than the VB to VB.NET conversion tools currently in existance.
>>
>>I hope the VFP community can grow through frustrated VB converts.
>>
>>Malcolm
>
>I would think that the design paradigms are so differnt, seeing that VB uses 'Cut&Paste' inheritance and VFP uses true inheritance, one would want to take advantage and retool and app from the gound up. I found that even translating FoxPro 2.x apps to VFP5 produced apps that were... less than appealing.
>JLK
>
>
>>
>>>>>Yea, but we're getting older every day ;
>Hey, As a new member of the Old Gezzer's Club I resemble that remark! :)