Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
drhoades32
Starting Member
8 Posts |
Posted - 2008-10-02 : 14:20:52
|
I went back into a Visual Studio report project today. I have made numerous changes to the stored procedure that populates the report but the name is the name as are the parameters. I cannot get it to run in the Data tab. I even rebooted my machine, just because, but that didn't fix it. I don't have any other reports to run because I'm relatively new here.I deleted the stored proc and added it back in. It still won't run and until I get it to run here and update the fields (though they haven't changed), the report won't run. The major "odd" thing I put in the proc is that I was creating a table, populating and deleting. Didn't work well for multiple hits so I changed the table to #nisse (which I found on the Internet somewhere). Does anyone think this #nisse--which solved my multiple hit issue--thing is adversely affecting the report?I'm on VS2005 and SQL Server 2005 and I upgraded it to SP2 this morning.Any info would be greatly appreciated. drhoades32 |
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2008-10-06 : 17:03:57
|
Reports generally don't like temp tables, but you can get it to work with them sometimes. Open the report in VS, go into the data tab and execute the stored proc from there. |
 |
|
|
|
|