In an ASP.NET app, I am trying to use a DBC-resident sProc as one might, e.g, in SQL Server... to return a cursor... to an ADO.NET OleDataAdapter.

A quick check w/ MS support says that that is not possible... even though the wording that the VFP7 helpfile contains implies that it is (the wording is: "...the stored procedures return results in rowsets...". MS support says that that does not mean that the results are returned AS rowsets). Apparently their wording describes how the 1st record of a rowset is used to return a single (scalar) value.

a) This was disappointing... but one suggestion was to try using CURSORTOXML to workaround the limitation. Unfortunately, CURSORTOXML does not seem to be supported by the OLEDB provider (I get a 'feature not available' error).

b) So... I thought, no prob, I'll simply create a temptable named w/ a sessionID, and then (even though it'll require a 2nd access) I can use a 2nd ADO.NET call to retrieve the temp table contents, getting around the VFPOLEDB limitation.

Well.. big surprise. The current problem is that the VFPOLEDB provider also apparently cannot support indirection.. that is, I can not use either &, EVAL, or _VFP.docmd() to execute a dynamically built SQL SELECT string (which my sProc composes from it's parameters).

This means that the VFPOLEDB provider is effectively useless for this purpose.

Comments? Am I missing something?

-bob