Hey John

My project details are unimportant. My point was this: .Net with C# is impressive. It has much to offer. But compared to VFP, it requires more resources (read programming time). For small shops, it is a very burdensome overhead. If you are the government or work for a big budget corporation, then C# is your game.

For building a data centric application, with n-tier construction and using OOP methodolgies, VFP still can't be beat for getting a completed project in the hands of the customers.

I have noticed that the .Net folks assume that using VFP means using a VFP backend. Many folks that responded appear to think that using VFP still requires @ SAY..GET command structure (Yes, I exagerate a little to make a point). Someone even mentioned how much easier it is to build Web apps with .Net (really?, Oh Duh).

I would like to have .Net advantages, but the speed of development with VFP.
Why couldn't a modern day Fox Technologies develop a new Fox that would compile on the .Net CLR?

An idea worth exploring. I'll start a separate thread for this.

Regards
Don Lowrey