I'm attempting to run a VFP stored procedure using the OLEDB provider for VFP and the ADO command object. Doesn't seem to work.

If I set the command to:

"MyStoredProc('SomeParameter')"

where MyStoredProc is the name of a real Sproc, I get a single rowed RS back with a single boolean field called "return_value" whose value is set to true.

It does not matter if I return another value from the sproc, the value is always true.

To test if the sproc was even running, I misspelled the name, and sure enough got an OLEDB Error "Program MyMisspelledSproc is not found".

Ok, fixed the name, and put some garbage code that should cause a syntax error in the Proc. Then I get an error that says "feature is not available".

I have been successful in operating on VFP data with the new provider by passing in SQL statements, but the sprocs thing is tripping me up. The OLEDB provider entry in the new VFP help file is still empty- does this mean I shouldn't be messing with it? If I remember correctly, some Softy said at one point or another that sprocs would be supported in the VFP OLEDB provider... did I remember incorrectly?