>>>>>>Hi,
>>>>>>
>>>>>>I've been working on a local report and created a stored procedure which accepts a parameter and pulls back the relevant records. I have configured my report viewer on a form and load the data up like this:
>>>>>>
>>>>>>

>>>>>>invoicesReportTableAdapter.Fill(dataset.InvoicesSelectByManifestNumber, this.manifestNumber);

>>>>>>
>>>>>>Prior to making some changes to the underlying stored procedure everything was working great. I then realized I had pulled out an incorrect field and missed two others that I needed for the report. I changed the SP and reconfigured the xsd by editing it and choosing to configure it again. But whenever that line of code runs, it takes a few seconds and then my application shuts down before it returns. No error message. Any idea what this could be or how to debug it?
>>>>>
>>>>>Stop the debugger just before this line.
>>>>>Run SQL Profiler and then step down in debugger, see what is sent to SQL Server.
>>>>>You can copy and run this code with SSMS.
>>>>
>>>>Hmmm, I can't find SQL Profiler. Is that not part of SQL Server Express 2008 R2?
>>>
>>>Nope,
>>>Profiler doesn't exists in Express editions :o(
>>>Don't you have another edition of SQL Server?
>>>Developer, Standard...?
>>
>>:) I've run the profiler, but have no idea of what I'm looking at so I need to do some research into how to interpret it. Any pointers to a good description?
>
>Run the profiler and select default tracing.
>Just before continue the problem line, clear trace window, then return back in C# and step down one line (execute Fill() line). Then return to SQL Profiler and see what is sent to SQL Server.

This got sent:

exec dbo.InvoicesSelectByManifestNumber @awb_manifestnumber=73358

which looks correct and when I copy that into SSMS and run it it returns what I expect. :{