::Not in all cases. Yes, VFP is very fast, but for some complex SQL operations, the SQL optimizer is a lot smarter than VFPs.

I'd be interested to happen upon some detailed info in this regard someday.



::It has to do with the conection pooling, memory allocation, etc.

Makes sense to me. This is what adventurous architecting is all about, isn't it? <g>



::Well, that's why SQL Server is more robust. You don't need to do any internal mirroring.

Do we know for certain that MSDE/SQLS don't do internal mirroring in order to achieve reliability?



::You can build a lot of logic in SQL Server SPs, and then return one or several resultsets (cursors in VFP parlance).

As you can with VFPDS -- I'm still not seeing the difference.



::once you actually know all that MSDE/SQL can do

So build all those great features -- and more -- into VFPDS! <g>



::one of Jim Duffy's ... sessions

I guess I wouldn't mind seeing one, just to see what he's talking about.

p.s. I'm still grateful for your article -- thanks again.