>>>>>Also, you may try running SQL Server profiler to see what is send to SQL Server when this call is initiated.
>>>>
>>>>Been there, did that - I'm trying to trace the flow of this process and this right here is a big holes. Somewhere, somehow it gets to the SQL statement and I'm trying to find that.
>>>>I have searched TFS 'til I'm about ready to puke and I've found the file where a call to the Stored Proc is made, but I don't know if it's the one actually being called from the form
>>>>It's not my code - it's not my portal - it's not the droid I'm looking for.
>>>
>>>If you found the call to the stored procedure and can confirm using SQL Profiler that this is indeed the procedure being called, I guess you found what you needed to find.
>>
>>No, I found a file where the call to the stored proc is made, but I haven't found any call to that file - or any mention of that file in any of the other code.
>
>As Craig suggested - look at the Service Reference. That will tell you where the method is actually run. If the server side is not part of your solution then you can't see the code....
That's also part of my fun, since I'm on the VFP side of the street, I'm thinking this machine isn't set up properly for the .Net side and I'm having issues opening the solution file from TFS.
"You don't manage people. You manage things - people you lead" Adm. Grace Hopper
Pflugerville, between a Rock and a Weird Place