>What do you mean does not support direct calls?
>Mark

You can only call them as part of a query. For instance:

SQLEXEC(nConnectionHandle, "select stored_procedure() from table_with_desired_number_of_rows")

You can not do the following:

SQLEXEC(nConnectionHandle, "stored_procedure()")

Anytime you ask about stored procedures and other capabilities of the VFP ODBC driver, you must be sure to explicitly say so because most people on UT who use SPs use client server SQL engines that provide greater functionality. Their replies may not apply to the VFP ODBC driver.

In Your system32 directory is a file named Drvvfp.hlp. This is the help file that describes the capabilities of the driver. The interpreter in the driver runs off the soure stored in the DBC, not the compiled code. This interpreter has no support for preprosessor directive, class declarations, and many other features. I have noted 2 errors in the documentation. Pcount() is not supported, even though it is not in the unsupported commands list. Use is not supported even thought it is in the supported commands list (also in the unsupported commands list).

When an unsupported command is seen by the interpreter, it returns the -1. The only way I've come up with to detect the location of the offending command is to comment out the function code and systematically uncomment the code until you find the offending statement. This is very awkward because the odbc driver stays attached to the vfp dev. system even afer the sql connection is closed. This means that you must exit and restart vfp after each run until you have isolated the errors.

Good luck.