>>
Because its very simple to create a large database application and very simple to create a small database application.
>>

Simple to create a large db application? What if I have db requirements that require tables > 2gb? Sure, I can partition tables in Fox - but then I have issues with indexes. No Mike...creating large db's in Fox is not "simple". In fact, it requires one to exact much more effort than what should be necessary.

Also, what if I need security and robust tx handling abilities. Fox can't do that.

>>
The syntax doesn't require a prohibitive object model,
>>

What exactly do you mean here? Are you saying that an extensive/rich object model is antithetical to working with data? This is an intersting comment because many in the Fox world like to work with data objects. It is intresting in an OO world, you advocate that one should eschew objects.


>>
and deployment issues are a snap since you're just copying files and metadata.
>>

Really? At some point, you do need to install a runtime - or have you forgotten that one point? Also, what if you need to remotely administer data in many locations? That is anything but simple and easy.

>>
No server software or hardware. For my data uses, I think VFP's the best.
>>

So far, you have not proferred a single reason to support the premise that VFP does data "best".