bardecode.com
barcode reading software
  • Home
  • Download
  • Purchase
  • SDK Licensing
  • Pricing
    • Windows SDK Price List
    • Windows SDK with PDF Extension Price List
    • Linux SDK Price List
    • Linux SDK with PDF Extension Price List
    • PDF Extension For Windows Price List
    • Multi-Platform Toolkit for .NET Price List
    • BardecodeFiler Desktop Only Price List
    • BardecodeFiler Windows Service Price List
    • DOS Command Prompt Barcode Tool Price List
    • Terms and Conditions
    • Refund Policy
  • Products
    • Softek Barcode Reader Toolkit for Windows
    • Softek Barcode Reader Toolkit for Linux
    • BardecodeFiler Desktop App
    • BardecodeFiler Windows Service
    • Windows DOS Command Prompt Tool
    • Multi-platform barcode reader toolkit for .NET
    • Aquaforest’s Autobahn DX
  • Knowledge Base
    • Documentation
    • Specifications
  • News
  • Contact
    • About Us
    • Terms and Conditions
    • Resellers
    • Links
Select Page ...

News

Common error when using the COM object

admin November 27, 2012 Software Development Kits No Comments

We often get emails asking why the ScanBarCode method in the SoftekATL.Barcode OCX object returns the value 0 when it works fine in other interfaces. The reason for this is that in the COM interface the number of barcodes found by the ScanBarCode method is stored in the BarCodeCount property.

For example, the following code is wrong….

oBarcode = New SoftekATL.CBarcode

nBarcodes = oBarcode.ScanBarCode(Path.ToString)

And should look like…oBarcode.ScanBarCode(Path.ToString)

oBarcode = New SoftekATL.CBarcode

oBarcode.ScanBarCode(Path.ToString)

nBarCodes = oBarcode.BarCodeCount
So the solution is simply to use the BarCodeCount property rather than the return code from ScanBarCode.
← QR Codes… Past, Present and Future
Android Barcode Reading – Quick Start Guide →
admin

  • Copyright © 2023 Softek Software Ltd. All Rights Reserved