Hi Robert
dont worry about mis-statments or understandings of this stuff. This is a discussion/education thread so we are all learning here...

I need to run right now... But wanted to address one comment and open it up for a little more exploration....


>>4) Your last assertion, although can be handled by VFP, is not >>reasonable. Why just a SQL backend for this type of debate, if you want >>to couch things to make .NET look good why not make it so the app has to >>be scalable to 100K users. .NET does SQL Server, VFP does SQL Server, >>most VFP programs do not need to add extra layers for data, more time, >>more technologies, more hassle, more training, more support???? I realize >>some of you have 'requirements' to use SQL or need additional features vthat make SQL more desireable in some situations, but why bother for most.
>>>>
>>My take is that the majority of VFP developers work with small to medium >>sized companies where I can see very little advantage in .NET, and if >>they need to do the SQL thing, there is reasonable support for this.
>>

According to ken a majority of VFP developers use SQL (or some equivalent) as a back end database. So this would be a good comparison. .NET Does not have a local engine like fox so we would need to end the discussion right there if that is the comparison. I don't feel we need to discuss the benefits/costs of using DBF's vs SQL in this discussion. It is a technology discussion. Thoughts ?


Thanks
Rodman