I have a Visual Studio 2010 VB.NET application that includes embedded .rpt files. One of the rpt files includes several subreports. Saving the main report in Visual Studio takes about 100 seconds. After several hours of analysis and trying the suggestions found at this forum (make sure the Verify on Every Print is unchecked, Page Setup No Printer is checked, update to 13.0.5, etc.) I've not been able to resolve the problem.
The delay seems to be related to a large number of parameters in the main report's stored procedure AND the main report includes at least one subreport. I've re-created the above with a simplified report and stored procedure that includes a single subreport. The main report displays the current date, page number and the embedded subreport. The subreport is blank and does not accept parameters. The main stored procedure includes ~135 parameters (none of which are actually used in the sp). With this scenario, save operations of the main report in visual studio take 100 seconds. If I reduce the number of parameters to ~105, save operations take about 50 seconds. If I reduce the number of parameters to ~75, save operations take about 20 seconds. If I reduce the number of parameters to ~45, save operations take about 7 seconds.
If I remove the subreport from the main report, the main report saves in less than 2 seconds (stored procedure has ~135 parameters).
If I reduce the number of parameters (~15) in the stored procedure and include the subreport, the main reports saves in ~2 seconds.
At runtime the report encounters a similar delay. In the debugger the entire delay occurs on the setting of the first parameter value (ReportClass.SetParameterValue). The first parameter is an integer. There is no delay when setting the other 134 parameters (integers, varchars and datetimes).