The documentation for the new VFP OLEDB driver says the following:
The stored procedures return results in rowsets, and are able to accept parameters.
I take this to mean that if I have a stored procedure called MySproc that runs a simple SELECT query, I can use ADO code like this:
Set oRecordset = oConnection.Execute("MySproc()"
and return the results of the query to an ADO Recordset via the VFP OLEDB driver. SQL Server sprocs work this way. In my testing however, the recordset returned is not the results of the query. Instead, it's a one record, one field recordset containing the return value of the sproc.
Does anyone know if what I want to do is possible? I haven't found much documentation for how to utilize the driver via ADO. Any help is appreciated.
The stored procedures return results in rowsets, and are able to accept parameters.
I take this to mean that if I have a stored procedure called MySproc that runs a simple SELECT query, I can use ADO code like this:
Set oRecordset = oConnection.Execute("MySproc()"
and return the results of the query to an ADO Recordset via the VFP OLEDB driver. SQL Server sprocs work this way. In my testing however, the recordset returned is not the results of the query. Instead, it's a one record, one field recordset containing the return value of the sproc.
Does anyone know if what I want to do is possible? I haven't found much documentation for how to utilize the driver via ADO. Any help is appreciated.