Scan as dark as you can to get a good image for ICR as handprint tends to ne thinner and lighter than machine printed text. Scan at 300 DPI rather 200 dpi and see if that improves the accuracy. be very specific with the zone ICR rules and only specify the exact character types (digits, upper, lower etc) you are expecting, rather than using 'All'. Make sure that the ICR zones have a reasonable amount of whitepsace around them.

Direct link to FAQ

Scan at 300 DPI rather 200 dpi and see if that improves the accuracy. be very specific with the zone OCR rules and only specify the exact character types (digits, upper, lower etc) you are expecting, rather than using 'All'. Make sure that the ICR zones have a reasonable amount of whitepsace around them.

Direct link to FAQ

Make sure that there is a reasonable amount of white space around each OMR zone.

Direct link to FAQ

First make sure that you applied all of the OmniPage Pro service packs to the software. Second check that OmniPage Pro actually runs on its own properly, as it sometimes may display an error message that could help with troubleshooting this problem.

Direct link to FAQ

EzeScan is required to have local administrator access to be installed.

EzeScan installs into the following locations.

For XP & Server 2003

install drive:\Program Files\Outback Imaging\EzeScan 4.2

install drive:\Documents and Settings\All Users\Application Data\Outback Imaging\EzeScan

For Windows 7, Vista and Server 2008

install drive:\Program Files\Outback Imaging\EzeScan 4.2

install drive:\ProgramData\Outback Imaging\EzeScan

Direct link to FAQ

 

For Windows XP and Server 2003

The user must be able to have manage access to the C:\Documents and Settings\All Users\Outback Imaging\EzeScan directory and it's subdirectories.

For Windows 7, Vista and Server 2008 

The user must be able to have manage access to the C:\ProgramData\Outback Imaging\EzeScan directory and it's subdirectories.

Please Note: This is if EzeScan is configured with the default setting of Workstation based settings. If using the application or current user directory the respective manage permissions need to be applied.

Direct link to FAQ

 

Please take a look at this link:

Direct link to FAQ

 

How do I stop Interwoven Worksite from reporting my document type as UNKNOWN?

The following new section must be added to the end of the existing nrt.ini file (located in c:\windows or c:\winnt):

Note The values PDF  or ACROBAT, TIF or TIFF must match the values that Worksite 8.X is using in it windows applications list. The values are customisable in Worksite, so they may have different values to the samples shown above.

It will mostly likely be

[EzeScan]
.pdf=ACROBAT
.tif=TIFF

or could also be

[EzeScan]
.pdf=PDF
.tif=TIF

Please contact us if none of the above options work.

Direct link to FAQ

 

Queensland State Archives have recently published a Digitisation Guildeline which is available at:

Direct link to FAQ

 

Yes, but we don't recommend doing this as the database files may become very big, causing poor database performance and system backups may take too long to complete.  Do this at your own risk!  That said, here is here is how to do it. 

The SQL Server database column must be setup as a varbinary(max) or image type. The Oracle Server database column must be setup as a BLOB.

Please note if you are using Oracle you must use the Oracle Oracle ODBC driver, not the Microsoft Oracle ODBC driver. The Microsoft Oracle ODBC driver does not support loading images into a BLOB.

There are two options that can be used.

    1) Use the EzeScan UPDATE_WITH_IMAGE placeholder.

    2) Use the EzeScan <<DOCBLOBDATA>> placeholder.

Option 1)

In the example the operator runs an insert statement to firstly upload the data, and then a select statement to select the row which UPDATE_WITH_IMAGE is used to pass the document in.

e.g.

insert into dbo.invoices (supplier, invno, invdate, invamount, transactionid) values ('<<Supplier Name>>','<<Invoice Number>>','<<Date>>','<<Amount>>','<<Transaction ID>>');

UPDATE_WITH_IMAGE select invfile, transactionid from dbo.invoices where transactionid = '<<Transaction ID>>';

Please Note: In this example the column transactionid is the primary key, it is recommended to include the primary key column in the update_with_image statement.

Option 2)

The placeholder <<DOCBLOBDATA>> can be used. This option is designed if the operator wishes to call a stored procedure (so therefore everything is done in one statement in EzeScan) or instead of using UPDATE_WITH_IMAGE (option 1) the insert statement can call the <<DOCBLOBDATA>> placeholder directly.

e.g.

call poc_upload.upload_claim_doc('<<(Field 1)>>,'<<DOCBLOBDATA>>')

Please note:

- If using Oracle with option 2 the operator must use single quotes around the <<DOCBLOBDATA>> placeholder.

- If using SQL with option 2 the operator must prefix a 0x in front of the <<DOCBLOBDATA>> placeholder.

- It is not possible to populate a BLOB parameter when calling an Oracle Stored Procedure using the Oracle ODBC Driver. Use NVARCHAR2 instead.

- The Oracle ODBC Driver is only capable of passing parameters values of up to 32k in size. As soon as you exceed this limit the driver crashes EzeScan. Due to this limitation it is not recommend to use a stored procedure with DOCBLOBDATA with EzeScan. Use the UPDATE_WITH_IMAGE option instead.

Direct link to FAQ

Pages