>
> I have already done accessing VFP tables via SP in DBC.
> It works well. I am yet to try accessing VFP via Com object, I really don't know which method is better.
>

I think it depends on what You want to return. You can't for instance return a cursor from a COM-Server, nor a DataSet as VFP does not know DS's (I didn't try, but I guess that's the way it is.) You could return an ADO-Recordset but that wouldn't be an ADO.NET Recordset. on the other side XML will be no problem.

I'd say, as long as You simply need plain data OLEDB will do well, despite things with a complicated Business-logic are probably better handled via COM (something like "SaveCustomerRecord()") where things are better encapsulated. Though You can do a lot via the stored Procedures.

It somehow leads to the philosophic question "Where does the Business-logic belong to". If You keep it in the StoredProcedures, it's tight to VFP, as You'd have to rewrite it when moving to another Database. Others say it belongs to the DATA.