>I will probably receive numerous ugly responses to this one, but in my dream world VFP is in dotnet. The ide anyway. I would love to have dotnet and vfp in one tool. However, I don't want to lose anything. (OK, I'm REALLY dreaming now). Let me do it either way. Delphi 8 has done that and the latest Delphi Informant magazine gives an excellent example of creating a data-driven app in Delphi 8. I don't want to give up the ease of doing things as I can in VFP but I want the ability to do web apps easily too like it can be done in dotnet. I'd rather not use two separate tools (well perhaps languages is the better term, maybe 3 in this case, ASP, VB or C#, and VFP) in order to create a web-based client as well as a fat client for the same data.

The ironic thing is how everyone used to pan VFP cause it didn't compile to "native" code but to op code which ran in a runtime. Now, we have the CLR which is quite similar to the VFP runtime.

BTW: You can use VFP for your middle tier and .Net for your web ui. You can create an SOA layer creating Web Services with VFP, or you could use COM interop. Unfortunatly both of these use COM which is an extra layer of performance sucking communication code. But, what can you do?

BOb