Clifford Lane
Top achievements
Rank 1
Rank 1
Clifford Lane
asked on 18 May 2010, 07:07 PM
I hope I can explain this so that it is understandable.
I have a report call it report1 that includes 16 subreports. When creating the subreports I did not use the report wizard but manually added the SQLDatadapter to the report setting up the connection that was needed. I did this with each of the reports, each of which is based on a stored procedure. Report1 ran fine and gave us the results needed. I then turned these over to someone to migrate to production.
The approach taken was to manually set the SQLconnection value in each of the reports to a web.config connection.string value. The result was fine. There was one issue with one of the reports that needed correcting. Using the production ready files I opened REPORT1 file and received an 'object not set' error for each of the subreports. the line referenced what the line getting the connection string value. I changed each report bacl to a 'hard coded' connection string value and was able to visualize the report again. Note that each individual report could be opened in design mode but the file containing the subreports would not open without errors.
Is there some way around this design time issue?
I have a report call it report1 that includes 16 subreports. When creating the subreports I did not use the report wizard but manually added the SQLDatadapter to the report setting up the connection that was needed. I did this with each of the reports, each of which is based on a stored procedure. Report1 ran fine and gave us the results needed. I then turned these over to someone to migrate to production.
The approach taken was to manually set the SQLconnection value in each of the reports to a web.config connection.string value. The result was fine. There was one issue with one of the reports that needed correcting. Using the production ready files I opened REPORT1 file and received an 'object not set' error for each of the subreports. the line referenced what the line getting the connection string value. I changed each report bacl to a 'hard coded' connection string value and was able to visualize the report again. Note that each individual report could be opened in design mode but the file containing the subreports would not open without errors.
Is there some way around this design time issue?
1 Answer, 1 is accepted
0
Hi Clifford Lane,
The following KB articles should shed more light on why this is happening: Using connectionStrings from configuration file.
Greetings,
Steve
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
The following KB articles should shed more light on why this is happening: Using connectionStrings from configuration file.
Greetings,
Steve
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.