08-23-2011 08:56 AM
I have a rather obsure issue in the sense that I use an industry version of ACT! and form filling software called Laser App; however I hope that these conditions won't prevent me from procuring a solution.
08-24-2011 06:46 AM
Welcome to the Sage ACT! Online Community!
I'm not familiar with this particular error, but check for the following:
Does your database contain a field with the exact name 'Zip Code'? If not, try creating one for Contacts, Companies, and Groups. It may be that the process is looking for that specific name and not finding it. This would be done through the Tools > Define Fields option.
08-24-2011 07:18 AM
Contacts and Companies did already contain fields called 'Zip Code.' The Groups field was named 'Zip,' and I changed it to 'Zip Code' but recieved the same error message upon attempting the Launch Laser App button again.
Next I tried changing the newly renamed Group 'Zip Code' field back to 'Zip' and creating an entirely new field named 'Zip Code.' The error message still appears.
Thanks for your timely response.
08-24-2011 07:30 AM
ALSO - I'm not sure if this is helpful, but it is bound to be related: when first I open my database, a dialog box pops up that says
"The following fields were not mapped correctly:
08-25-2011 05:29 AM
That is helpful to know. When the message is issued upon launching ACT!, it usually indicates that a field with that exact name does not exist within the database. The 'field audit' function within the Fin Pro version is looking for that field. It sounds like you have verified that the field does exist - but make sure it is an exact match including upper/lower case characters.
Was this database converted from another version of ACT!?
08-25-2011 07:16 AM
The database was converted from another version of ACT - originally it was made in ACT 6 and Financial Professionals is the first update since.
I have double and tripled checked that the characters used to spell out the field are accurate.
08-25-2011 01:32 PM
08-26-2011 07:35 AM
Thanks for your help. We do Check and Repair on a regular basis, I actually just ran it yesterday.
I opened the demo database and upon clicking the button was prompted to first configure the database to work with LaserApp - I assume that means the error is specific to our database as you suggest.