We normally suggest using black pages as separators. However you could also use white pages but these can get confused with the document pages, and blank pages. Any colour that scans bitonally as black (i.e. red, blue etc) could be used as a separator page. We suggest setting the percentage white space for separators at 10%.

Direct link to FAQ

A blank page is a page that is usualy around 99.80% white. The operator can change this percentage value of white for a blank page can adjusted in the Admin->Jobs->Enhancement tab. It is recommended not to set this setting below 99.70% as pages that may contain a small amount of content could be deleted.

To remove blank pages at scan time simply tick the 'Delete Blank Pages' option tickbox on the Enhancement tab of the Operator Actions form (F2). Otherwise you can use the Shift and Delete keys to delete blank pages from a batch set of images.

If an image has a dark line around the edge of the page or has black spots from the hole punch and EzeScan is not deleting it, the H Area % and V Area % can also be set in the Enhancement tab. H Area is for Horizontal and V Area is for Vertical. i.e. if setting the V area to around 85% EzeScan will ignore the top and bottom 7.5% of the page therefore not picking up the black coverage and deleting the page correctly.

Direct link to FAQ

According to the ScanSoft Knowledge base you simply need to rename the opodma.dll file as opodma.old.

Direct link to FAQ

The information on this page has moved, please click here to go to the new location here.

Direct link to FAQ

Please make sure that you correctly setup the DCOM settings for the TRIMMaster, TRIMWorkgroup, TRIMEvent processes as per the instructions on pages 27-41 of the TRIM Context Install Guide.  One possible workaround is to make sure that the TRIM application has already been launched on the EzeScan PC.

Direct link to FAQ

Applies to: EzeScan 4.3.60 and above

If there is a requirement to have EzeScan run a spell check on words outside of the standard dictionary it is possible to add these words into one of them.

You can create a new custom dictionary by using an existing dictionary (e.g. US/UK) and adding words to it by following the steps below:

  1. Admin -> Spelling Dictionaries - Select an dictionary and click export
  2. Select a location and press save
  3. Open the document in notepad (note the syntax)
  4. Open your custom words from your other source and copy them onto the bottom of this document and then save and close the file.
  5. Admin -> Spelling Dictionaries - Select Custom and click Import
  6. Browse to your new file and select it. Click ok on the message to overwrite the dictionary.

To enable from KFI

  1. Admin -> KFI -> Fields Tab -> Edit on your field -> Automation Tab
  2. For the setting Spell check input data using dictionary -> Set to custom
  3. Click OK, apply and OK

When you run the job the value in the field will be checked against the dictionary.

 

Direct link to FAQ

This is most likely because you have unticked the "Use ADF" option which sets the "Pages To Scan" value to 1 page at a time. Simply tick the "Use ADF" option and make sure that "Pages To Scan" value is set to a value greater than 1.

Direct link to FAQ

First you might like to take a look at the following web site articles:

Here are some useful suggestions:

  • Barcodes could be applied using pre printed labels, or printed on documents at 600 dpi on a laser printer. Printing them on poor quality paper or on a bubble jet would be a definite no no. Any ink bleed between vertical lines in the barcode will cause problems.
  • A barcode printed using a small font will have a problem when scanned because the white space between the black lines becomes harder to see. If the lines look like they  are touching each other in the scanned image, the recognition will most likely fail. Using  a larger font or point size can help to spread the lines out in the barcode. Fine barcodes should be scanned at a minimum of 300 dpi, 400 dpi would be better but the resulting large image size may slow the process down too much. It's best to start with a large fort that works and gradually decrease it's size until it doesn't, and then increase the size back up 1 or 2 sizes from that failure point.
  • What font is best?. No easy answer here. Depends on how much data you want to put in the barcode, and what software tools you have purchased to produce your barcodes. It looks like code 3 of 9 is a reasonable choice, but EAN 8/13 could be better. An important factor is that you should use a barcode that is designed for that industry segment or packaging requirement.
  • If the barcode doesn't work you will need to increase the font size up to 24 or 26 point to get it to work okay.
  • If the barcodes are poor quality then you must specify the barcode type on the Profiling Tab within EzeScan. You must not try to use UNKNOWN type when running the job in production. The UNKNOWN option is normally used to just help identify what type of barcodes are being read. Once this is determined the barcode type should be set to that specific type.
  • If you are using 3 of 9 barcodes did you remember to add the "*" character to the start and end of the value you are putting in the barcode? For example let's say your barcode value is "123456789",  then the value placed in the barcode label is actually "*123456789*". The start and end "*" characters are required by the barcode recognition engine, but they are discarded from the returned value of "123456789". These characters are not normally required when using other barcode types.
Direct link to FAQ

The most likely cause of this problem is that the EzeScan DWORD entry is missing from the HKEY_CURRENT_USERS\Software\Xerox\DocuShare Client\DsOdma\SupportedEditors registry key. Simply use regedit to add a DWORD named "EzeScan" and sets it's value = 1.

Direct link to FAQ

1. The Audit database is only active if you are licensed for the AUDIT module and your job/route has "Update Audit Database' set.

2. As of 4.0.844 It contains 3 tables (Note: the Jobtype_Statistics table is no longer used/written to)

[Completed_Work] with the following columns in it:

  • ID (AutoNumber)
  • Date_Time (DateTime)
  • Module_Type (Text)
  • Job_Type (Text)
  • Other_Destination (Text)
  • Input_Filename (Text)
  • Input_Directory (Text)
  • Output_Filename (Text)
  • Output_Directory (Text)
  • Output_Email_Address (Text)
  • Output_FtpServer_Address (Text)
  • Output_File_Format (Text)
  • Output_File_Size (Number)
  • Number_Of_Pages (Number)
  • Elapsed_Time (Number)
  • Routing_Rulename (Text)
  • Processed_By (Text)
  • KFI_Index_File (Text)
  • KFI_Index_File2 (Text)
  • Key_Strokes (Number)
  • Workstation_Name (Text)
  • Operator Name (Text)
  • Zone_Errors (Number)
  • Scanner_Settings (Text)
  • Enhancement_Settings (Text)

[Current_Work] with the following columns in it:

  • ID (AutoNumber)
  • Job_Type (Text)
  • Module_Type (Text)
  • Job_Type (Text)
  • Workstation_Name (Text)
  • Operator_Name (Text)
  • Date_Time (DateTime)

[Deleted_Work] with the following columns in it:

  • ID (AutoNumber)
  • Job_Type (Text)
  • Module_Type (Text)
  • Job_Type (Text)
  • Workstation_Name (Text)
  • Operator_Name (Text)
  • Date_Time (DateTime)

3. When Ezescan is installed the default Admin-Options form, Audit database settings are set to use a local copy of the Ezescan_Audit MS Access database. 

4. If you want to use a centralised Audit Database with several Ezescan workstations you could simply place the Ezescan_Audit MS Access database file (Ezescan_Audit.mdb) onto a network shared drive, and then configure each of the PC's Admin->Options, Audit tab settings to use that network shared database file.  This is only recommend for low volume usage, with a small number of Ezescan PC's.

5. If there a large number of Ezescan PC's then a better option, would be to create an Audit database on a networked MS SQL Server and then configure the EzeScan Audit Database ODBC connection to use that database rather than the local or network shared EzeScan_Audit.mdb file. FAQ #55 provides information on how to do this.

Direct link to FAQ

Pages