April 4, 2014 at 12:43 pm
I'm using VS 2005 Report Designer. All I need to do to finish a report is show data (from a stored procedure) in a table on a sub form. However, no data ever shows up, even though it appears in the "Data" pane. Data also appears when I run the procedure in SSMS.
I am very familiar with this technology. I have created reports before. I just can't figure out why I can't get this stored procedure to populate detail rows of a table on my sub report.
The stored procedure accepts a parameter that comes from another dataset. I have dropped a text box on the report to display the value of the parameter and it appears.
In the stored procedure I stuff a debugging table (i.e., create table debug (mystr varchar(255))) with values from data in the stored proc. When I run the report from VS Report Designer this table is being filled with the right data.
I drop the table on the sub report. I put in header data. In the detail section I drop one or two fields from the dataset in question. Every time I run the report I see the header data but never the detail data.
Jeez Louise, Report Designer sure is difficult to work with. Does anyone have a potential remedy?
Thanks,
April 4, 2014 at 1:02 pm
Visibility of the detail row of the table in question is set with Hidden = false. The same setting is for both detail columns. Same with the table itself.
Does anyone else think Report Designer is buggy?
April 4, 2014 at 1:20 pm
Well, suddenly it works. I created another stored procedure that was a skeleton of what I need. In the "Data" pane I changed the dataset's reference to this skeleton proc. Then I ran the report a couple of times. Then I changed the dataset to point back to the intended procedure. Hooray! This only took hours to accomplish.
April 4, 2014 at 2:05 pm
Once again the table won't populate. I wonder how Microsoft can get away releasing something as buggy as Report Designer. I have spent a day and half over issues that appear to be coming from Report Designer.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply