>>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?

Yep. It has been in my experience. Plus its pretty easy to upsize the database and leave the app as is.

>>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.

I mean that I can type:

use myapp!mytable
replace status with "BAD" for lastpayment > GOMONTH(DATE(), -1) and balance > 0
use in mytable

And thats all it takes to run database commands. The flexibility to work nose to nose with the data like this or with OO in between is something I find very useful.

>>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".

Lol. Whatever, guy.

The way you argue your points and nitpick others makes you the Michael Moore of the UT, you know.