Scannable Office Frequently Asked Questions
In Form Publisher, the document I have designed comes up blank. Where did it go?
Everything is still there but it’s hidden. Check two things: In the View menu, select Page Layout. If the screen is still blank, from the Tools menu select Options. In the View tab under Show, put a check in the box next to Drawings.
When I scan my form into Form Reader, I get the error message "Error initializing the Association file."
This error message means that someone has opened the Associate.mdb file and modified the tables. To reset the Associate.mdb file you will first need to delete the Associate.mdb file. This file is usually located in the "C:\Program Files\AutoData Systems\AutoData Scannable Office" folder. Next, go into Data Mapper and from the Edit menu select Association Database. Data Mapper automatically recreates the Associate.mdb file. Now you can go back into Form Reader and begin scanning.
When publishing my form in Form Publisher, I get the error message, "Error 6, OVERFLOW".
This is an issue from an older version of Form Publisher. Go to www.AutoData.com and from the support area, go to the update section and download the latest update. The update will prevent this problem from happening again.
When I scan my form into Form Reader I get the error message, “Target Database Error Number 3075 Syntax error in query expression…”.
The reason this is happening is because someone has put an illegal character in a folder name (C:\John’s Surveys\Employee Satisfaction\Comment.tif). Notice in the path that an apostrophe has been put in the name of the folder “John’s Surveys”. This path cannot be used for an image capture field because when Form Reader tries to write the data to the Access database, Access will not allow this path because it contains an illegal character. To fix this problem you should first take the illegal character out of the folder name. Next go into the Form Publisher document and correct the path for the image capture fields, save and republish the document. Finally, you will need to edit the Associate.mdb file. Open Data Mapper and from the Edit menu select Association Database. Edit the path in the Association Database to show the correct path to the Form File and Map File. Click OK and close Data Mapper and you should now be ready to continue scanning.
Creating my database I get the error message “Error Number 3191 cannot define field more than once”.
There are two possible reasons you are getting this message. First, check to make sure you didn’t name two fields the same name when you were defining your form. It is highly unlikely that this mistake was made in Form Publisher because Form Publisher will not allow you to put two fields with the same name on the form. The second possible reason could also be connected to Form Publisher. If you use the Allow Multiple Marks option for a Check Mark Field and do not select Treat As One Field the database is going to create a separate field for each bubble. When a new field is created for each bubble it uses the field name and numerically increments each option. For example, if the field is named Q1 (for question one) and there are five different bubbles, the database will have five fields named Q11, Q12, Q13, Q14, and Q15. If you have other questions named Q11 – Q15 it will not create the database because it would have duplicate field names. The only way around this is to change the field names to accommodate for the multiple mark fields. For example name Q11 – Q15, QuestionEleven – QuestionFifteen.
When I scan my form into Form Reader, I get the error message "Target Database Error Number 3464 Data type mismatch in criteria expression."
This error will happen when Form Reader tries to write letters to a number field in the database or spreadsheet. You cannot write letters to a field in a database or spreadsheet that is expecting numeric data. Another possible reason you would get this error message is if you are using a key entry field and a Microsoft Excel spreadsheet. If you are using Microsoft Excel do not use any punctuation characters or symbols.
Form Reader is not reading bubbles that are marked and when the verification window comes up the bubbles are not lining up with the yellow boxes.
A reason this can happen goes back to when the form was being designed in Form Publisher. When you place OMR bubbles on a form they are in a table. The default cell alignment in the table is set to "Align Top Left". If the cell alignment is changed to align the bubbles any other way in the cells, the software will still think the bubbles are in the top left area of the cell. To fix this problem highlight the cells and change the cell alignment back to "Align Top Left".
I installed WinFax PRO version 10 on my workstation and when I try processing the faxes in Form Reader I get the message, "error getting faxed page. Error Number: 5. Invalid procedure call or argument."
This is an issue with version 10 of WinFax PRO. In Form Reader select Options from the Tools menu. In the Process tab change the Form ID setting to Recognize Old Style Locators. Click Ok and before trying to process the faxed documents remember to mark the messages as unread in the WinFax PRO Message Manager.
I designed a multiple page document in Form Publisher and when I publish the document all of the fields are pulled to the first page.
This is a problem that can occur when some fields are grouped together. To resolve this problem select all of the fields on each page and ungroup them. After you have done this, save the document and it will publish without pulling the fields to the first page.
One of the options for a checkmark field has a label that wrap to the next line. Is this ok?
It is ok for a response label to wrap to the next line however you do need to manually adjust the row of the table for this option. To do this select the bottom line of the row and pull it down. Now when the form is published it will be read correctly by Form Reader.