Is This any good to you
If so I can forward you the file
========================================================================
Active Barcode Component : Version 4.2
========================================================================
Please turn on Word-wrap to read this document.
Note that this product will behave as a testware version unless valid licence codes are entered during Setup.
Testware versions have a portion of the barcode missing.
These notes apply to all Active Barcode Components, using Active Barcode Component - Universal as an example. The control names are:
Active Barcode Component - Universal = axbarcode.ocx
Active Barcode Component - Code 39 = abc39.ocx
Active Barcode Component - Code 128 = abc128.ocx
Active Barcode Component - EAN/UPC = abcean.ocx
Active Barcode Component - ITF = abcitf.ocx
This product is suitable for Windows 98/2000/XP/2003/Vista or later.
Active Barcode Component may be registered with your computers operating system in three ways:
1. Self-registration during setup. Your own software setup program should self-register the component, just as the dLSoft one should. This does not always work!
2. Registering from within another program. Many major programs (eg. Word, VB, Delphi) now contain menu items for registering controls or components. Essentially you just use the browse button to find the AXBARCODE.OCX file and the program will then register the component.
3. Manual registration. From a command prompt in the installation directory, run
Regsvr32 axbarcode.ocx
Using the component.
The components are specifically designed for use with Visual Basic 6 and VBA (eg. in Microsoft Access). We are not able to supply sample code for use in other environments.
The component may be used as an Automation object (eg. selecting Insert Object from a program Edit or Insert menu), or as an Active-X control by adding it to a form in Visual Basic, Borland's C++ Builder or Delphi, or within Container application such as Word and Access. In Access the Caption property can become bound to a data field as the Control Source.
Note that this is a developers product. Only the developer can use the product in design mode. Developers may not distribute the design time licence. Only the run-time file (.OCX) may be distributed.
Release notes:
version 4.2
Modified to allow operation under UAC in Vista.
Version 4.1
The USPS OneCode and China post codetypes have been added to the list of types supported by the 1D Universal version. The list of supported types shown on the 1D Universal version's property page now appears in alphabetical order.
Version 4.0
This version is a major re-write and is not a drop-in replacement for previous versions. Code 128 control parameters may now be user defined (although the defaults remain as before). See the Help file for details. The bitmap graphics functions now produce 1-bit 2-colour bitmaps for GIF and BMP filetypes and black & white bitmaps for PNG. The ID keys have been modified but we do not recommend using this version on the same machine as earlier versions.
v3.3 IATA 2 of 5 barcode and Japan Post code types added to ITF and Universal versions. See Barcode Help for details.
v3.2 All components marked as safe for initialising
Active Barcode Component - 1D Universal now support ISBN-13 barcodes. See Barcode Help for details.
v3.1: TargetHdpi and TargetVdpi properties added to allow bitmap images to be generated for a defined target resolution.
If installing after an earlier version, note that all projects will require the component to be deleted and re-added. In the case of Delphi, the AXBARCODELib_TLB files should be deleted, along with any package created, and the component reinstalled into Delphi.
In the case of Word 2000 the Axbarcodelib.* files must be deleted (usually in Windows System or Profile\user\local settings AND Word 8's temporary directory) and the component re-added to documents. If this is not done the macros may fail with a property error and the ActiveX property sheet will cause an exception which will require a restart of Windows.
For Excel and Access the earlier versions of the control must be removed from forms and added again - otherwise property errors will be encountered.
This release contains working samples for VB6, Access 2002/2003.
dLSoft November 2006
For support:
e-mail:
support@dlsoft.com