>>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
>
>Hmmm... I see what you want. That would be alot of work. All of the forms would have to be converted, all the data handling code converted to ADO.Net... then there is the issue that VFP is not strongly typed, that would be a heck of a hill to climb. You would be forced to declare all your variables, that's for sure.
>
>Jos... I doubt it will happen.
>
>BOb

BOb, well you see what I'm saying :) MikeH asked a question about who wants a .Net language like VFP. When people refer to a "VFP.Net" they are not saying they want to type "endif" instead of "end if". Thats pointless. They are saying that internally the "VFP.Net" would map current VFP commands to .Net framework classes.

Someone here on the forum has intimated that they are busy working on a VFP.Net type of product and I wouldnt be surprised if its along these lines. Although I agree it must be a monster job.

btw, did you read this message Message #917040 ? The truth is that it is possible. What MetinE and others have been saying is possible. But MS obviously must take a commericial viewpoint which we can all understand. But how amazing is that? Powerbuilder.Net. Geez dude, I definitely want to review that! And look at WebDev, a French product. The same dev tool runs code for Windows, .Net, Pocket PC, and they say they are looking at a Linux version. There is a way. But is there a will? Is there enough money in it?