Sorry, should have been more clear. In the past, my VFP SP's
would put a single row into a temp cursor, and from there all
the columns would get concatenated and delimited with a ~.
On the C# side of things, I would address the SP with an
ADO.NET ExecuteScalar(), to a ToString() on the returned
object, and then Split the string into an array on the ~.
From there I would work with the array elements.

This worked fine in the past, but it required a database call
for each thing. I thought I would speed things up by collecting
all of my input parameters on the C# side, passing it to my
VFP SP as a ~ delimited string, have the SP cut that into an
array, do all the SQL, and then return a DataReader that I could
iterate over.

But it looks like the OLEDB driver can't be used to return readers
from SPs....

Have you been able to return anything from a SP besides a string?

Thanks.


>>>Because VFP SPs are Procedures, just like any other VFP procedures. That function
>>>is returning the default value of .T., which C# is translating into "1".
>>My VFP SP's had always returned strings of delimited data (with ExecuteScalar)
>>that I parsed on the C# side, until now.
>
>I'm confused here: what were you doing before? How were you returning strings of delimited data, and why doesn't it work now?