Issue: Reports Do Not Display Correct Barcode Data in Version 15.6

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.

  1. 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.
  2. 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.

  3. Fig. 1

  4. Add a database relationship with OptimizationResults as the child table, and Parts as the parent table.
    1. Click the Dictionary tab in the lower right corner of the report designer.
    2. Right-click the dataset table for OptimizationResults and click “New Relation.”

    3. Fig. 2

    4. Enter the text string “Parts-OptimizationResults” as the property Name in Source.
    5. Enter “Parts” as the property for Name and Alias.
    6. Select “Parts” for the Parent DataSource property. The property for Child Data Source should already contain “OptimizationResults” if the steps above were correctly completed. 
    7. 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.
    8. 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. 
    9. Verify that your screen matches Figure 3 below.  

    10. Fig. 3
  5. Modify the databand definition of the table Parts to be OptimizationResults.
    1. Double-click the databand defined as Parts and click the tab Data Source.
    2. Double-click the dataset table OptimizationResults.
  6. 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.
    1. GroupHeader condition: {Parts.Name} Modify To: {OptimizationResults.Parts.Name}
    2. 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))}
    3. 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 + ")" 
  7. Click the Preview tab. Evaluate “Warnings,” “Information Messages,” and “Report Rendering Messages” for significance and correct as necessary. Correct any “Errors!”
  8. 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 ...
    • Reference: Common G-Code Filename Barcode Formats & Strings

      Various CNC machines differ in their part barcode requirements from the manufacturer, and also in the way they are set up by the machine technician. It is necessary to know those requirements when a part label is configured that contains a file name ...
    • Recent Articles

    • Toolbox Release Notes | Build 24.1.1105.641

      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 ...
    • Microvellum Foundation Library Release Notes | Build 24.1025

      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 ...
    • Toolbox Release Notes | Build 24.1.1030.641

      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 ...
    • Toolbox Release Notes | Build 24.1.1010.641

      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 ...
    • Toolbox Release Notes | Build 24.1.1001.641

      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 ...