Scanning in EOLF 4 - Annex F error
Posted: Thu Dec 11, 2008 4:12 pm
Hi All
We have a problem when scanning documents and then importing into EOLF. We get an Annex F error message and apparently this is to do with the default A4 page size on the scanners.
After testing all our scanners using the same document we receive the Annex F error.
The list of model numbers for all our scanners is below:
Lanier LD075
Lanier LD160
Lanier LD175
NRG MP7500
HP 4345 MFP
There are 3 different brands of scanners using their default A4 scanning options, I would expect 1 or 2, but 3... Surely something is not right.
We are aware that we can set up a special scan size which could be selected, or, we could convert from Adobe to Adobe to get around this problem BUT we are reluctant to add another step into our filing process because we want things to be faster (who doesn't?) and we didn't experience this problem in Version 3.0 using the same scanners.
Has anyone else had this problem? Does anyone have any suggestions on how to get around this, without adding an extra step/thing for our users to remember?
All help will be gratefully received as this is currently stopping us from upgrading to version 4.0.
Many thanks
Kelly
We have a problem when scanning documents and then importing into EOLF. We get an Annex F error message and apparently this is to do with the default A4 page size on the scanners.
After testing all our scanners using the same document we receive the Annex F error.
The list of model numbers for all our scanners is below:
Lanier LD075
Lanier LD160
Lanier LD175
NRG MP7500
HP 4345 MFP
There are 3 different brands of scanners using their default A4 scanning options, I would expect 1 or 2, but 3... Surely something is not right.
We are aware that we can set up a special scan size which could be selected, or, we could convert from Adobe to Adobe to get around this problem BUT we are reluctant to add another step into our filing process because we want things to be faster (who doesn't?) and we didn't experience this problem in Version 3.0 using the same scanners.
Has anyone else had this problem? Does anyone have any suggestions on how to get around this, without adding an extra step/thing for our users to remember?
All help will be gratefully received as this is currently stopping us from upgrading to version 4.0.
Many thanks
Kelly