Common Toolkit Errors and Issues

Information for the AccuZIP Toolkit standalone product, allowing the use of AccuZIP6 features in your own programs.

Moderators: Chrissy, Donna, MartyH

Post Reply
User avatar
Terry
Site Admin
Posts: 1983
Joined: Wed Sep 20, 2006 3:45 pm

Common Toolkit Errors and Issues

Post by Terry » Fri Nov 01, 2013 11:26 am

If you attempt to call the zp4connect in Step 2 of the documentation, and get an error:

Refer to the error codes on page 8. The most common error is #5, and in most cases, it means the path established in the code to the config.acu is invalid, or the contents of that file are invalid.

For example, if you had your config.acu in a directory called C:\AccuZIPToolkit, then you either need to declare a variable in your code using the "C:\AccuZIPToolkit\Config.acu" path, or your zp4connect call MUST read:

Code: Select all

nResult=AddrCode.zp4connect("C:\AccuZIPToolkit\Config.acu",ErrorMsg)
Where "ErrorMsg" is your variable for the error message displayed.

That allows the zp4connect function to properly locate the Config.acu file. If you still return an error, open the Config.acu and verify that the paths point to the correct locations for all files.

If you stored your USPS database files in the C:\AccuZIPToolkit\ folder, then your Config.acu would look something like this:

Code: Select all

[CONFIG]
NATIONAL=C:\AccuZIPToolkit\ADRDATA\National\
LOT=C:\AccuZIPToolkit\ADRDATA\National\
EWS=C:\AccuZIPToolkit\ADRDATA\National\
DPV=C:\AccuZIPToolkit\ADRDATA\dpv\
LACSLINK=C:\AccuZIPToolkit\ADRDATA\LACSLink\
SUITELINK=C:\AccuZIPToolkit\ADRDATA\SuiteLink\

[SYSTEM]
OUTPUT=C:\AccuZIPToolkit\Support\AddrCode.dbf
If you return an error 5 when calling zp4connect, either the system cannot find the Config.acu, or the Config.acu contents have incorrect path names.

If you return an error code 3, however, it's because the NATIONAL folder itself is read-only. Make sure the ADRDATA folder and all subfolders referenced in your config.acu have read/write permissions.

How to determine if records returned are good or bad
This question comes up periodically, especially if you use the Desktop Application as well. While the desktop application has a Errno_ field, the Toolkit return codes do not. You want to look at the DPV and the DPV Notes returns, which will tell you if the record returned good data, or had issues matching the address.[/b]

If your trial version date expired, but you are not getting the prompt to enter a new serial number for the full version subscription you purchased
Go into your AccuZIPToolkit\Support folder, and delete the AccuAddress.dat file. The next time you call the object, it will prompt for a serial number. Enter the serial number given to you at the time of purchase (or request a new one from support).

Post Reply