>>But, that requires SQL Server, right?

Yes.

>>Also, my backend remains VFP, so I am wondering if I could use that as well.

Nope. While the connection string does let you specify the OLEDB provider to use, it currently only works with SQL Server. From the SQLXML 3.0 help:

"Provides the PROGID of the OLE DB provider through which SQLXMLOLEDB executes the commands. In SQLXML version 2.0 and version 3.0, this property value is restricted to "SQLOLEDB"."

>> Otherwise, that would mean I would have to code everything that this one single function is doing, correct?

The object really doesn't do anything. It's the SQLXMLOLEDB OLEDB provider and a helper DLL that are really doing all of the work.

Maybe you could do something with a typed-dataset?

-Mike