>>>>>>>Post the result of this query

>>>>>>> SELECT @@Version,
>>>>>>>	SERVERPROPERTY('Edition') AS Edition,
>>>>>>>	SERVERPROPERTY('ProductVersion') AS ProductVersion,
>>>>>>>	SERVERPROPERTY('ProductLevel') AS ProductLevel

>>>>>>>
>>>>>>>If you're using version other than Express, go to Tools Menu in SSMS, SQL Server Profiler. Run the trace right before testing your procedure. Don't forget to pause/stop trace once done using the pause/stop buttons in the Run Trace dialog.
>>>>>>
>>>>>>Version: 2008R2
>>>>>>Edition: Standard
>>>>>>ProdVers: 10.50.1600.1
>>>>>>Level: RTM
>>>>>
>>>>>Apply Service Pack 2 for your version. With SQL Server it is always a good idea to stay current with SPs.
>>>>>
>>>>>Since you're using a standard edition, you can use SQL Profiler to see what exactly you're doing with your calls.
>>>>
>>>>SQL Profiler tells me nothing. As in I can't tell when the SP gets fired off from VFP.
>>>>
>>>>Downloading Service pack now
>>>
>>>What do you mean it tells you nothing? Do you see calls to your SP? Did you select proper columns and events for the trace? You can probably use the default T-SQL trace template.
>>
>>No, I didn't see a call to my SP
>>Yes, I used the default template
>
>Do you have batch completed and procedure completed events? These are the only two you need. If you don't see calls to your SP after you run the trace, then your SP is not called.

Then why is it saying that it can't find the SP on the 2nd time through? I do see connection_resets being called in the trace and the only SP I see being called is some generic getbatchid proc.