>?M.tiBatchID is being sent as a parameter. While you are correct in saying that the string should be built if you are using ADO, I am using SPT with VFP, and this will allow the sending as I have previously written.
>
>I am open to other ideas, and suggestions.
>
>Dave S.
Hmm, this is getting beyond my level of expertise. Do you have the same problem if you use a straight SQLEXEC() rather than a SQLPREPARE()/SQLEXEC() pair (albeit with a performance hit)?
If you use SQLPREPARE(), how do you pass the parameter with a later SQLEXEC()? Or does it simply depend on the variable existing and being in scope? Does your parameter go out of scope at any time?
On a more mundane level, what is your backend, and are you using up-to-date ODBC drivers?
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
