Quickstart#
Introduction#
Installation#
In order to use Perfect Address SDK, users must:
Run the same version of DLL (
UNZDLL32.DLL
,UNZDLL64.DLL
) and Database Files (Z1.dat - Z8.dat)
In order to remove (or “uninstall”) Perfect Address SDK:
The Perfect Address SDK has no uninstall program.
Delete the Perfect Address SDK folder (Example: c:pasdk) and all files it contains.
Remove
UNZDLL32.DLL
,UNZDLL64.DLL
, andUNZDLL.INI
from your Windows folder (usually named c:windows or c:winNT).
The SDK consists of a set of eight database files and a DLL search engine.
The SDK is available for download in two formats:
Installing the self-extracting version#
SDK.EXE#
If you download the self-extracting version of the SDK, “SDK.EXE”, the self-extracting program will install the DLL and database files for you in the folder you specify.
Download the self-extracting version of the SDK (“sdk.exe“). Right-click the sdk.exe and select “Run as Administrator” to begin install.
You may have a pop-up to allow this app to make changes to your device. click “Yes”.
This will bring up the Perfect Address SDK self-extractor installer - click “next”
Select the file path to extract the sdk files to by clicking “Browse” or pasting it in.
Check the box to create the directory if it does not already exist.
Click “Next”
Once installation is complete. it will display “SDK Setup. SDK setup completed successfully” Click “OK”.
Click To See Instructions With Screenshots
Download the self-extracting version of the SDK (“sdk.exe“). Right-click the sdk.exe and select “Run as Administrator” to begin install.
You may have a pop-up to allow this app to make changes to your device. click “Yes”.
This will bring up the Perfect Address SDK self-extractor installer - click “next”
Once installation is complete. it will display “SDK Setup. SDK setup completed successfully” Click “OK”.
If you do not run as adminstrator, you may receive an error during install.
SDK.ZIP#
Installing the PKZip archive version: SDK.ZIP
If you download the version compressed with WinZip you will have to de-compress the archive using PKZip, WinZip or some other decompression utility to extract the files.
Double-click the “
DLSetup.exe
” to begin silent installation.Download the “sdk.zip” file.
Right-click “sdk.zip” and select “Extract all…”
Open the Extracted sdk folder and right “
DLSetup.exe
” and select “Run as Administrator” to begin silent installation.Click “Yes” to allow app to make changes to your device.
Once installation is complete you will see “SDK Setup - SDK setup completed successfully”
The DLSetup.exe runs silently in about 1 second.
Warning - You’ll need about 650MB of free space on your hard drive to hold the decompressed SDK.
Click To See Instructions With Screenshots
DLSetup.exe
” and select “Run as Administrator” to begin silent installation.Double-click the DLSetup.exe to begin silent installation. Click “Yes” to allow app to make changes to your device.
Once installation is complete you will see “SDK Setup - SDK setup completed successfully”
Uninstallation#
Perfect Address Installation#
DLSETUP.EXE
to install the interactive version of Perfect Address..NET Wrapper Code#
New Manual Format#
SDKMAN.PDF
.Calling The DLL From Your Program#
Using Universal Naming Convention (UNC) Path Names#
Paths to the data files in a network environment follow Universal Naming Convention (UNC) rules. This means that you can specify a remote computer using its network name instead of mapping the remote computer to a local drive, as in:
\\Server\sdk\files
Using the Windows Registry#
The registry entries required are as follows:
- Add a new key:
HKEY_LOCAL_MACHINE\software\Melissa Data\PASDK
- Under the new key, add two string values:CDROMPathandDataPath
- For these values enter the appropriate UNC or direct paths, just as you would in the UNZDLL.INI file.For example:
\\data\e\zipdata\
- Add a binary value:MixedCaseEnter a binary value of 00 or 01, depending upon your mixed case preference. (1 == mixed case, 0 == all caps).
Update Installation#
When you receive a new release of the Perfect Address SDK, you must replace the old address database files and the DLL search engine.
Each version of the address database must match the DLL which is used to access it. This means that, as a minimum, you MUST install the proper DLL from the new version into the proper place (usually the Windows folder) on each client machine which must access the new address database. Failure to install the new DLL will cause the DLL initialization function to fail with error code 117.
Error code 117 indicates a version mismatch between the active DLL and the active address database. There are several reasons for this: we add new features to the SDK from time to time and we often change the format of the address database files.
This means that you (and, potentially, your customers) must install a new DLL with each new address database update.
An older DLL will not work with the new database files, and vice versa. However, we do retain the old function names and calling parameters, such that no programming changes are normally required to maintain compatibility.
However, Melissa does reserve the right to change the function names and their parameters at any time. You can simply copy the DLL file and the eight data files (Z1.DAT - Z8.DAT) from the new version to their proper places on your computer(s).
This can be accomplished using a simple script file. It is not necessary to run the setup program in this case, and no changes are required to the initialization file or the registry.
Initialization Woes#
c:\pasdk\samples
The “addr32.exe” Sample File#
The sample program named addr32.exe
is a good test program to try first. If it doesn’t give you a fill-in-the-blank form,
then the installation is probably bad. Try reinstalling the SDK in this case.
If you see a form and can enter and verify a sample address successfully, your installation is working okay, and your troubles are elsewhere.
Click To See Screenshots
Mathing the new database version to the DLL version being used#
If your problem comes later, perhaps when you install a new version of the SDK, the problem may be that the new database version doesn’t match the DLL version you are using.
Each month we release the SDK as a complete, matching set.
The database and the DLL for each month’s version of the SDK MUST be used together as a set.
Click To See Screenshots