Issue: Reports Do Not Display Correct Barcode Data in Version 15.6
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.
Cause:
Build 15.6 contains an expanded ability to process with multiple single parts processing stations. One of the reasons for this is that a User may want to direct the parts to one of the several CNC machines to equalize the workload of those machines.
When processing with multiple single parts processing stations, previously, the program would populate the barcodes to the Parts table only for the last station of multiple stations processed. This is because that table has only a single field for the barcode data. The Parts table design does not support optimized data produced by multiple stations.
Build 15.6 now makes it possible to obtain the correct barcode data in the report when using multiple stations but to support that change, the single parts barcode data is now populated to the OptimizationResults table instead of the Parts table.
Resolution:
Here is a tutorial for modifying the default “Parts Select Processing” report to consume the data populated to the new location. The procedure for custom reports will be similar, depending on the report structure.
- Open Toolbox and click: “Toolbox Setup > Design Reports > Design Manufacturing Report > New Report From Existing” select the report to use as the template for the new report.
- In the Report Setup screen, name the report as needed. Click the options button for “Microvellum Work Order” and make sure there is a checkmark next to OptimizationResults. Lastly, set the property “Is Batch Report” to True and click OK.
Fig. 1
- Add a database relationship with OptimizationResults as the child table, and Parts as the parent table.
- Click the Dictionary tab in the lower right corner of the report designer.
- Right-click the dataset table for OptimizationResults and click “New Relation.”
Fig. 2
- Enter the text string “Parts-OptimizationResults” as the property Name in Source.
- Enter “Parts” as the property for Name and Alias.
- Select “Parts” for the Parent DataSource property. The property for Child Data Source should already contain “OptimizationResults” if the steps above were correctly completed.
- Double-click “LinkID” from the right column of Parent Columns and verify that it is correctly populated to the left side of that same section.
- Double-click “LinkIDPart” from the right column of Child Columns and verify that it is correctly populated to the left side of that same section.
- Verify that your screen matches Figure 3 below.
Fig. 3
- Modify the databand definition of the table Parts to be OptimizationResults.
- Double-click the databand defined as Parts and click the tab Data Source.
- Double-click the dataset table OptimizationResults.
- Modify all text component expressions or data columns, databand group condition expressions or data columns, event code, and databand filter expressions to include the new relationship to OptimizationResults. See the examples below, contact Microvellum to arrange for Remote Services in making these modifications.
- GroupHeader condition: {Parts.Name} Modify To: {OptimizationResults.Parts.Name}
- Text component expression displaying cut part length: {IIF(Parts.AdjustedCutPartLength <> Nothing, MVValueFormat(Parts.AdjustedCutPartLength), MVValueFormat(Parts.CutPartLength))} Modify To: {IIF(OptimizationResults.Parts.AdjustedCutPartLength <> Nothing, MVValueFormat(OptimizationResults.Parts.AdjustedCutPartLength), MVValueFormat(OptimizationResults.Parts.CutPartLength))}
- Master Cut Report GroupHeader2 BeforePrint event code: varQtyItemNumberString = Me.varQtyItemNumberString + " #" + Parts.Products.ItemNumber + "(" + (Totals.Sum(GroupHeader2, Parts.Quantity) * Parts.Products.Quantity).ToString + ")" Modify To: Me.varQtyItemNumberString = Me.varQtyItemNumberString + " #" + OptimizationResults.Parts.Products.ItemNumber + "(" + (Totals.Sum(GroupHeader2, OptimizationResults.Parts.Quantity) * OptimizationResults.Parts.Products.Quantity).ToString + ")"
- Click the Preview tab. Evaluate “Warnings,” “Information Messages,” and “Report Rendering Messages” for significance and correct as necessary. Correct any “Errors!”
- Save the report using the small Save button in the extreme upper left corner of the report designer.
Updated default reports may be downloaded from the Downloads area of the Microvellum Knowledge Base.
Related Articles
Issue: Part Labels Display Incorrect Barcode Data when Processing to Multiple Machines in 15.6
As of build 15.6.221, you now may use the simplified procedure found in the Microvellum Help Center article Processing Station Associates for Reports (Overview) to resolve this issue in addition to the procedure found in this article. Issue : Part ...
Issue: Report Unexpectedly Missing Data
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 ...
Issue: HBore Barcodes Do Not Match Part Picture
As of build 15.6.2211, you now may use the simplified procedure found in the Microvellum Help Center article Processing Station Associates for Reports (Overview) to resolve this issue in addition to the procedure found in this article. Issue ...
Using Barcode Fonts "3 of 9" and "Code 128b" in Microvellum (Overview)
The Microvellum reports support a variety of barcode fonts to match the scanning requirements of many popular barcode scanning devices. The two fonts most often used are “3 of 9” (referred to as “Code 39” in this article), and “Code 128b.” This ...
Streamlined Label and Report Data Processing
We have streamlined the way information for labels and reports is processed to improve accuracy and efficiency. Part image rotation, filenames, barcodes, edge boring(Hbore), and edgebanding location data are all now accessed from ...
Recent Articles
Microvellum Release Notes | Build 26.1.0723.641
The following release notes apply to Microvellum build 26.1.0723.641. Function UI Update The Function Arguments interface has received a major visual overhaul to improve the usability, clarity, and visibility of several elements. Input fields are now ...
Microvellum Release Notes | Build 26.1.0702.641
Dark Mode Fig. 1: The MV Palette in Dark Mode. To enhance the user experience when working within Microvellum, a new Dark Mode setting has been added to the software. Enabling this will apply a dark theme to most interfaces, allowing for a greater ...
Microvellum Foundation Library Release Notes | Build 26.0630
Additions: Added new Fixture product Die Wall Advanced. This product takes the legacy Die Wall products to a new level. More features and advanced parametric abilities: Up to five individual unique subassembly segments, widths controlled via ...
Microvellum Foundation Library Release Notes | Build 26.0527
The following release notes apply to the Microvellum Foundation Library build 26.0527. Additions Added new features for the Wood Drawer Box to have reduced sides, sub front, or back. Added 3 new global and subassembly prompts: “Wood Drawer Side ...
Microvellum Release Notes | Build 26.1.0529.641
The following release notes apply to Microvellum build 26.1.0529.641. BSB Docking Size Fix An issue was reported to be occurring in Microvellum BSB 2026: when adjusting the size of a docked Microvellum palette, users found that the palette would ...