The following printer families are supported :
|TSC||Zebra||Any Windows Printer Driver|
This version includes the following new printers :
- Cab A8/300
Below is a summary of some of the new features available in EASYLABEL 5.0:
New Database features
- Access to any database that includes an OLE-DB data provider. This includes Microsoft Access (.MDB), Oracle, and Microsoft SQL Server. This is faster than using an ODBC driver.
- New database editor allows updating any database that can be accessed by EASYLABEL.
- The database editor allows for the creation of database cross references, where an item in a database record can point to one or more records in another table or database.
New Field Types
- Added two new types of label fields: multi-source text and multi-source barcode. A multi-source field can pull data from several sources and combine them into one field. This is similar to a “linked” field but is more powerful and has no built in limitations on the number of items that can be combined.
- A new EAN-128/UCC-128 wizard allows easy creation of barcodes that may contain multiple application identifiers (AI’s) that are derived from multiple data sources.
Updated User Sign-on and Password Options
- User ID and passwords have been expanded and can now be up to 16 characters long.
- New User Name and User Description fields have been added to the user configuration screen.
- Administrator can select minimum length for User ID and Password
- Administrator can set a password expiration by number of days so that users are forced to change passwords periodically.
- User accounts can be set so that the password never expires.
- User accounts can be “locked” so that the User-ID cannot be used until it is unlocked.
- Administrator can set a password re-use policy to prevent users from reusing old passwords.
- New “complex password” option to force passwords to contain at least one numeric or other special character.
- New user authorization to enable or disable user ability to change their password during login.
- New user authorization to enable or disable user ability to delete files using the software’s delete function.
New User Logging Options
- Logging of changes to user configuration (add/change/delete)
- Logging of user events: login success, login failure, logoff and password changed.
- Added the option to set the location of the user log file.
- Added the option to set the maximum size of the user log file
- Added the option to set if user log file will wrap (overwrite old events) if log reaches maximum size.
- New log file viewer to view on screen or create printed reports of user logs.
New Label Format Options
- Added the ability to create an image file (in several different image file formats) of a label format. use “Save Label Image” from the “File” menu.
- Added the option to require user to enter a comment when label format is saved. the comment should describe the reason the label format was changed. this also saves the User-ID of the person who made the change.
- Added the option to save history of all changes made to a label format. this creates a backup format file anytime the format is saved. This option can be specified for each format file and also has a global option to enable/disable for specified formats. the location of backup format files can be specified by the system administrator.
- Added the option to save an image file (EMF) for all print jobs. this creates an image of the first label of the job to be printed. the name of this file can be automatically generated or can be specified by a field on the format. the name is saved in the format tracking report. can be specified for each format file and also has a global option to enable/disable for specified formats. the location of the print image files can be specified by the system administrator.
Other Logging Options
- A delete log will record the user, date, time, and pathname of any files deleted using the software’s delete function. The location of the log can be specified by the system administrator.
- database logging will copy any updated database records to another database to keep a historical record of database changes. the location of the database logs can be specified by the system administrator.