>>Oh put the sample I sent in first message to a DBC that you create - say myDBC.dbc. Then :
>>
>>open data myDBC
>>GetCustomerDetails('BERGS','myCheck')
>>select myCheck
>>browse
>
>Cetin,
>
>I don't want to do OPEN DATABASE. I want to do it all by SPT. I was able to put a procedure in the database. With open database I called the procedure. It returned the cursor with the correct data. What I can't get is what am I missing to make that jump? I can do SQLEXEC(nHndl, "SELECT.....", 'cursor') I want to replace the "SELECT....." with a call to the SP.
>
>Thanks for you patience
>Mike

Mike,
This way or that way (open database or some other call opens the database) to use an SP you open the DBC. It might not be open database and say from an ASP page ADO connection :

oADOconn.ConnectionString = "Provider=VFPOLEDB.1;Data Source=" & cCacheDir & cDestDB
...
oRS.Execute("myStoredProc(param)")

even opens/close database implicitly. Or say you use a table from a DBC, you don't say open database but dbc is opened.

If you mean you want to execute an SP with SPT AFAIK with VFP ODBC driver it's not supported. It's supported with VFPOLEDB driver and backend servers.
With backend servers (like MSSQLserver) you can :
Create and call a permanent SP (provided you have rights)
Create and call a temporary SP on the fly (and even that temporary procedure might be created for all users connected or only for you)
Cetin