Hi
In all replies I can read the same, the need for strong typing, the need for ADO.NET, ...
I don't believe that VFP cannot be ported to NET platform as it is. I don't believe that the engine cannot be ported also (exists already Codebase NET). I've seen entire IDEs built on NET platform, or games. Why an interpreted xBase language cannot be built/ported? (I bet that runtimes will be very small)
So, IMO, it is possible but will never happen.


>>>
>>>Hi Bob. The point thats being missed is this: if VFP was by some magic able to create .Net assemblies then one wouldnt need to learn the framework class libraries - one would just need to know VFP commands and functions and the final app would be a .Net managed code app. The VFP commands and functions would worry about what framework class libraries are needed. (Keep in mind that its a theorectical discussion :) Hence it would be a reduced learning curve for a VFP developer.
>>>
>>>Now, its 11:50pm. Portugal beat England. And I'm off to bed :)
>>>
>>>Later.
>>
>>Had lunch today with a guy who's company uses Powerbuilder (to which many, like George T, would say "yuk!" *grin* ). They are beta-testing Powerbuilder.NET, the language construct has stayed pretty much the same.
>>
>>And he hasn't had to learn the framework classes, from what I gathered.
>
>Well thats something isn't it? Amazing really. Which is exactly what my answer to MikeH's question was really about.