Hi Gerard,

You've received already a number of answers, but really is missing some of the differences. A very skewed comparison so far, if you ask me.

>Security ?
VFP has little to none. no comparison.

>Speed ?
Hmmm that is an interesting one. It depends on what you do with it. For mainstream SQL statements SQL server is far superiour over any network though there are some little comments to make.

Most applications use the DML locally, such as on local cursors. VFP is faster doing that as it has less internal rules to comply to. No security, flat table layout, simpler and faster lookups, direct index access.

However what everyone else seems to fail to notion is that VFP does have a very good record based DML. This means that record by record operations are MUCH easier in VFP than in SQL. Direct access to the internal schema (e.g. the indexes) makes optization possible for those problems that ask for a record oriented approach. Commands like SCAN, LOCATE, SET ORDER, SEEK, INDEXSEEK and clauses like NEXT xx, FOR and WHILE do not have a direct equivalent and prove their value in certain situations. In this area VFPs database engine is superiour, but its applicability is limited since the majority of the world is doing SET ORIENTED DML. Both have their value nonetheless and can be used efficiently if chosen as a solution for the right problem.

>Ease of Use ?
Again, what do you want to do with it. Personally I find it a USE mytable followed by a BROWSE FOR.... and manually changine the fields I want. a lot esier than first doing a SQL SELECT and then a UPDATE SET and a next SQL SELECT to check whether everything went fine. But of course the ones who never were familiar with using VFP in such a interactive way would not know much better, huh ?

>Robustness ?
SQL server, however, it sometimes feels like using a sledgehammer to drive a nail in. For a simple mom and pop app, i'd probably would not user SQL server. Using DBFS possibly with an upsizing strategy would be my first choice.

>Scalability ?
SQL server, no doubt. However never misuse this argument. A hairdresser on the corner is not likely going to demand a SQL server version that has to operate through the internet via 40 different offices. Scalability is an advantage in certain cases. In most cases, it is just not an issue.

>Ease of getting data in and Out ?
VFP, hands down... USE, COPY TO, APPEND FROM, IMPORT, EXPORT.

I'll add FLEXIBILITY
VFP hands down, just because you've got a rich OO language integrated with a database language. VFP is a complete programming tool that allows you to directly program on data. With SQL server you're disconnected from a rich OO language. You need another tool for supplementing.

You can use VFPs database engine to solve puzzles in cursors. I've written little short programs to calculate prime numbers, solve sodoky puzzles, number crunching etc. VFP really shines in this area.

Walter,