Thank you Sergey for the very helpful info, this does clear this up and answer my question on the different forms. As always you continue to provide very keen insight to everyone here. I suspected a bug too, and felt compelled to see if someone else might have had a similar experience. The distribution and development configuration make it difficult for me to test.

Thanks
John

>Hi John,
>
>When you use Procedure Call Escape Sequence

SQLEXEC(oApp.ch,"{CALL vsp_woValid(?lcJOBID,?lcEqid)}")

ODBC driver has to convert it to the syntax of the backend DB. Theoretically, you can use the same Escape Sequence stored procedure call for diferent backends. I didn't try it so I don't know how well it works in real life.
>
>If you're using only one backend than SPT form

SQLEXEC(oApp.ch,"EXEC vsp_WoValid ?lcJOBID,?lcEqid")

is preferable. In this case ODBC driver only has to substitute parameters and sends result command to the backend DB. It's easier to copy between SQL Server QA and VFP and easier to read.
>
>In regard to the problem with WinXP SP1, I guess it's a bug introduced by SP1. I don't have access to WinXP so I cannot verify that. Maybe somebody else can do that.
>
>>Has anyone else observed this behavior?
>>
>>Building an .exe with VFP 7.0 SP1 and utilizing SQL Server 2000 SP2. I have no other configurations to test.
>>
>>In Windows XP the following line of code will not work in XP Service Pack 1 but does work for XP without SP1 and all prior versions of Windows.
>>
>>

>>SQLEXEC(oApp.ch,"{CALL vsp_woValid(?lcJOBID,?lcEqid)}")
>>

>>This line of code does work for all versions of Windows including XP SP1.
>>

>>SQLEXEC(oApp.ch,"EXEC vsp_WoValid ?lcJOBID,?lcEqid")
>>

>>
>>Is there any advantage to using one method over the other? Perhaps Microsoft is no longer going to support the call functionality and I failed to catch that somewhere? Any thoughts or insights would be greatly appreciated.
>>
>>Thank You