New Error in Code

Spence · Post by **Spence** » Tue Dec 12, 2006 12:16 am

Our reports have worked flawlessly and we never fault them.

Until today :/

We use the Report.Show() function to preview our reports. This has never been an issue. However, we run through the standard processes, which is
Report.regdata(ds)
Report.load(file)
Report.Show()

This used to work flawlessly, and show the report in a print preview stage. This now however spawns no new window. No error message. The code calls the .show() method and returns normally.

To print, we would use:
Report.Render()
Dim PrinterSettings As PrinterSettings = New PrinterSettings
PrinterSettings.Copies = 1
Report.Print(PrinterSettings)

This however now calls the .Print() line and shows a messagebox (generated by stimulsoft) of "Object Reference not set to reference to object", and then does not print the document.

The strange thing is this; If we use the the report preview pane control, then the reports preview and print fine. If we use the export features: ie
Dim PdfExport As StiPdfExportService = New StiPdfExportService
PdfExport.ExportPdf(Report, ExportFile)

Then this will correctly generate the report.
We're at a loss, and with no source code have no where left to turn. We are using stimulsoft v1.50, .net 1.1.

Thanks in advance.

Post by **Edward** » Tue Dec 12, 2006 3:21 am

What were the reasons for changing the report behavior? May be you did updates for the new version or something else.

Thank you.

Spence · Post by **Spence** » Tue Dec 12, 2006 7:19 pm

We released an update and everything appeared to be fine. Its simply the stimulsoft windows through the report.show() method does not show any more, and directly printing the report also fails.

We have not altered the reports themselves, nor the data schema being placed into them. As I said before, using other methods of getting at the reports, such as the stimulsoft preview pane, or the export functionality shows the reports generating fine, but we cannot use the report.show() or report.print() function. It has occured in all our installed software instances, and all our systems, and we are at a loss to explain it. Is there any further info we can gather in regards to enabling debugging or some such so that we can see where it is failing?

Spence · Post by **Spence** » Tue Dec 12, 2006 9:14 pm

I'll enter this here FYI for anyone who's interested. We were using a weakly typed dataset and used a Select * to fill a query. When these were null, the report would not show in the designer correctly, stating that the columns were not in the dataset returned. When I placed the columns in there, then the report worked perfectly.

I had totally forgotten about the text in the debugging console

Post by **Edward** » Wed Dec 13, 2006 4:07 am

Ok.

If some unexpected issues will appear when you work with the new version, please contact us to

to resolve any issues with the report creation.

Thank you.