Version 5.13.0.1635

Released: 2/08/2012

The following printer families are supported:

Avery Dennison

cab/Gemini

Citizen

C.Itoh

Datamax/Fargo

Godex

HP

Intermec

Novexx

Postscript

Printronix

RJS

Sato

Systemwave

TEC

Tharo

TSC

Zebra/Eltron

Any Windows Printer Driver

This version includes the following new printer:

Sato GY412 (Dual sided direct thermal)

Important Note: As of Version 5.7.0 EASYLABEL will only install on Windows 2000 or higher. Windows 95, Windows 98, Windows ME and Windows NT are no longer supported. EASYLABEL 5.6 should be used on Windows 98, Windows ME and Windows NT. Windows 95 is not supported.

Important Note: If you used Visual Studio 2003 to compile a project using EASYLABEL’s ActiveX objects with version 1.1 of the .NET framework, you may experience a crash when you run your project after upgrading to EASYLABEL 5.7.0 or higher. This is because the project tries to load .NET framework version 1.1 and then tries to load .NET framework version 2. This loading of the second .NET framework fails and that causes the crash. To correct this, compile your project using Visual Studio 2005. If this is not possible you can correct the problem if you un-install version 1.1 of the .NET framework.

VoiceCode is a trademark of YottaMark, Inc.

The following changes/additions have been made:

  1. New VoiceCode Field Type

Added a new field type ‘VoiceCode’ to create the 4 digit code needed to integrate with voice picking systems popular in large warehouse management systems (WMS). The data for the VoiceCode is a GTIN and Lot Code with an optional date. This data can be any data source supported by EASYLABEL.

  1. cab Printers New ‘Label Buffer’ Setting

Added option for cab printers to select multiple/single buffer modes. By selecting single buffer mode, labels with date and/or time fields will be updated at the time they are printed. Using multiple buffer mode may be faster, but the date or time on the labels may not be updated as often.

  1. New EPC Schemas

Added the following new EPC schemas to the RFID wizard: SGTIN-198, SGLN-195, GRAI-170, GIAI-202, GDTI-96, GDTI-113, and GSRN-96. To encode a schema larger than 96 bits you need to be sure that the RFID tag supports an EPC memory bank large enough to hold the desired schema.

  1. RFID Tag User Memory Bank

For printers that support writing to the ‘User Memory’ bank of an RFID tag, the RFID wizard will allow entry of data to be written to the tag user memory. Not all RFID printers support this feature.

  1. Advanced RFID Tag Password and Locking

Added the option of using advanced 32-bit locking and kill passwords. Also added support for locking and unlocking each individual memory bank of the RFID tag. These features may not supported on all RFID enabled printers.

  1. Windows Printers and Custom Form Sizes

With some Windows printer drivers, EASYLABEL did not support all of the custom form sizes that could be created in the printer driver. This has been fixed so that these custom form sizes are available to be selected in EASYLABEL when designing a label format.

  1. Tharo H and V Series Printers and PDF-417

There was a bug in the driver when printing PDF-417 symbols that were linked from multiple pieces of data and one or more of the pieces changed from label to label. The data in the symbol was incorrect. This has been fixed so that the correct symbol is generated.

  1. Problem With Increment/Decrement Minimum/Maximum

In some cases, the min/max values remain in effect when the source of data is changed to one that does not allow specifying an increment or decrement. This caused the field value to change. This has been fixed so that min/max values are ignored if the data source disallows increment or decrement.

  1. Datamax 600 DPI Printers

On Datamax 600 DPI printers UPC or EAN barcodes would print narrower than they were displayed on screen. This has been fixed so that the screen representation is more accurate with respect to the printed output.

  1. Format Definition Reports

In rare cases EASYLABEL may crash or fail to create a format definition report for some label format files. This was caused by invalid fields in the label format. EASYLABEL has been changed to skip over fields that don’t contain valid data, allowing a definition report to be created.

  1. cab Printer and GS1-128 Barcodes in Standalone Mode

The cab printer driver has been changed to allow downloading label formats that contain GS1-128 barcodes which have variable data. The printer will calculate any needed Mod 10 check digits based on the variable data.

  1. Database Search Fields

In the field list under “Source of Data / Database” any fields that are database search keys are shown as bold font for the field name. This makes it easy to see which fields represent search fields for the database.

  1. Source of Data is “Database”

In cases where the last used connection string for a database was very long (over 300 characters), EASYLABEL may crash when creating new fields and setting the source of data to “Database”. This has been fixed to allow connections strings up to 1000 characters long.

  1. Multi-User and Minimized Window Setting

By editing the shortcut you can start the program minimized. This is useful for command file monitoring. This worked for all versions of EASYLABEL except Multi-User. This has been fixed so that Multi-User can be started minimized.

  1. Using a “When-Printed” Date

In some cases where a date was entered and was then copied to another field to be formatted, the day may change if the time is near midnight. This was caused by daylight savings offsets of the hour. This has been fixed so that the date printed is the same as the entered date.

  1. cab Printers

In rare cases where each label batch needed to be sent to the printer separately, sometimes batches after the first batch were not formatted correctly. This has been fixed.

  1. SQL Databases

When connecting to some data sources, invalid SQL statements might be created. This caused problems when trying to create a field using that data source. This was caused by improper quoting of identifiers in the SQL statements. This has been fixed.