Gene

I think your points are the right ones. VB and ADO is "best" if you want to use MS tools, *not* for technical reasons, but because you can be sure that you don't have to keep looking over your shoulder and the clients' "perception" is positive.

The fact is that as soon as you start using DO...WHILE or IF...THEN...ENDIF in FP, the efficiency of the result suffers. The speed differences are visible in some cases. In addition, the ability of SCAN to index optimise some expressions, an ability that IF and DO certainly do not have, can provide order of magnitide differences. So the petty "gee, only one extra line!" examples we've seen here miss the point completely.

For me, the *big* issue is the method concurrency one. If you can't have concurrent methods then VFP under MTS is a dopey option. Better to but $200 extra RAM and use a pool server- foxisapi.dll works quite nicely under IIS2.0 and allows VFP to return speeds of 4X VB with ADO in our tests.

That Service providers won't look at VFP is an excellent proof of just how well the product is promulgated by its vendor.

As for ADO, well, my company uses it in Java (Supercede using JADO which is ADO written in Java)- not the latest spec, but pretty good. It works. I'm not biased.

If I were biased, I would have added a few SCATTER MEMVAR MEMO, INSERT INTO... FROM MEMVAR statements against a 100-field table to show how "easy" it is to use ADO- "with just one extra line of code!!!!!"

Regards

JR