1) Well VFP doesnt easily get connected to outside of VFP.
1a) VFP smokes ACCESS in all respects

2) Yes, MS bought VFP for the bitmap indexing code which now resides
in SQL.

3) SQL has BCP

4) SQL has DTS. no comparison, no Data Junction is NO comparison.

5) The SQL query processor, page handler, optimizer, parser smoke VFP on multi-table joins.

6) SQL scales. 2 CPUS smoke 1, 4 CPUs smoke 2, etc.

7) SQL kicks #$% in OLAP. VFP is a no go there.

8) SQL COSTS ALOT MORE!

9) SQL/VFP is a good C/S combo.

10) SQL indexed views smoke VFP

11) SQL has the AGENT to schedule jobs

12) SQL has SQL-DMO

13) SQL advanced stuff: check contraints, computed columns

14) MS will eventually kill VFP as SQL takes its place (MSDE)

15) VFP OOP features are very good if you plan lots of projects
in VFP, subclassing etc. SQL doesnt talk anything but SQL.

16) VFP cant get slammer type worms.

17) SQL/VFP both have XML

Hey i used both for years.
Its the project size dude.
VFP you can afford
SQL the company needs to buy.....