Some Users tell us that infrequently a report may be displayed that is missing data when previewed. There are various possible reasons for this issue, but one cause may be a defective report dataset definition.
This article explains a pre-test to apply to your report to determine if this may be the issue, and then the procedure for fixing the issue if the test is positive.
Symptom : Missing data on a rendered report.
Pre-Test : Open the report in the Report Designer and use the View Data command to verify that data exists in each dataset table.
Resolution : Redefine the dataset definitions of the tables that are blank.
See the tutorials below for the steps to perform in the Pre-Test and the Resolution above.
Pre-Test Tutorial
Open Toolbox and click: “Toolbox Setup > Design Reports > Design Manufacturing Report (or the report type needed).”
Click “Open Report,” select the report that is unexpectedly missing data, select the work order and batch if applicable, and click “Designer” to open the report in the report designer.
Click the “Dictionary” tab in the lower right corner of the designer, expand “Data Sources > NewDataSet.”
Right-click on each table to confirm that the resulting grid contains data. If the resulting data grid looks like Figure 1, it is OK. If it is blank and looks like Figure 2, the dataset definition needs to be repaired.
Fig. 1
Fig. 2
If the data grid is blank like Figure 2, proceed with the “Resolution Tutorial” below. Otherwise, look elsewhere for a solution to the missing data.
Resolution Tutorial
If you have the report open in the report designer, close it and open it again in the Report Viewer, so you see the rendered report.
Click the button: “Edit Data Source” and click the database type for the offending table found in the pre-test above.
Fig. 3
Uncheck the checkbox for the offending table, and click OK.
Open the again in the Report Viewer, so you see the rendered report.
Click the button: “Edit Data Source” again and click the database type for the same offending table.
Check the checkbox ON for the table, and click OK.
Repeat the Pre-Test above to verify the issue has been fixed.
This procedure redefines the dataset as defined in the factory database.
This issue happens infrequently, so if you can duplicate the broken dataset, send us the procedure you used to break the report. We would love to hear from you in the comments section below.
Watch the attached video to see a demonstration of the tutorials in this article.
Issue Any report or database that references the field PartsProcessingStations.LinkIDBatch data will fail to display data. An example of a default Microvellum report that was left inoperative by this database change is the “ Master Cut Report – ...
Symptom: Reports displaying barcode data from the Parts table are inconsistent or incorrect. This issue has a different cause than when a Part Label displays incorrect face 5 or face 6 barcode data. Click here for more information about that issue. ...
Symptom You have created a custom part label, but when you print the labels, an extra blank label is printed at the beginning or end of the series of labels. Resolution 1 If the label contains group header bands, set the GroupHeaderBand property ...
If you have been working on a custom report and after saving it you get an unhandled exception error when you try to reopen it, you probably want to know if there is a way to fix that error. The answer to that question depends on whether you know the ...
The articles in this section of the Knowledge Base involve working with Lists for display in your reports. To learn more about Lists and how to access the Report Designer, see Creating Lists in Report Designer. This article provides information for ...
The following release notes apply to Toolbox build 24.1.1105.641 Nesting Fix Fig. 1: The fatal error that would occur during processing. There was reportedly an issue that occurred when clients attempted to process a work order using the nesting ...
The following release notes apply to Microvellum Foundation Library build 24.1025. Additions Added new global variable “Remove Stop Dado On Bottom Edge” for wood drawer boxes. Check this option to run the dado through at the bottom of the sub front ...
The following release notes apply to Toolbox build 24.1.1030.641 Routing and Profile Fixes Several issues were found with routing and polyline paths: Fig. 1: Horizontal routes off of a part disappearing (left) and appearing correctly (right). When ...
The following release notes apply to Toolbox build 24.1.1010.641 Biesse Winstore Fix Several issues with the Biesse Winstore plugin have been resolved: There was an issue that would sometimes occur wherein materials that were intended to stack wound ...
The following release notes apply to Toolbox build 24.1.1001.641 HBore Toolfile Fix Fig. 1: The location in the Toolfile UI where the error would occur. There was an issue reported with the functionality of the Horizontal Boring Machine setting in ...