Build 1191 Released 9/07

AddressCheck Interface – A few Canadian Addresses are not returning a status code:

Solution:
This will be fixed in the next release.

Work-Around:
Do not write the Company field back into your data. It will never be changed for corrected.

Work-Around:
Do not write the city back into your data if the address does not code. If you want the city for the given zip code even though the address is not valid, you can look it up in the ZipCodeData interface.

Solution:
This has been fixed in the next release. Please download the latest version of Address Object on the main Address Object Support Page.
 

Build 1115 Released 4/07

AddressCheck Interface – The Canadian Post Office has informed us that a number of records in the Canadian data files for the province of Quebec are missing data for the street direction of approximately 50 streets. In certain cases, previously existing street direction indicators were dropped from street addresses and a few street names were incorrectly modified. The impact of the problem is low and mail processing and mail delivery should not be affected providing the mail piece bears the correct postal code.

Solution:
The specific records have since been corrected and will be available in the next release.
 

Build 1091 Released 12/06

Address Object for Unix does not contain the following properties:
GetCanadianDatabaseDate()
GetCanadianExpirationDate()

Work-around:
Make sure to update your Canadian data files every time you receive them. They are released each month so if you have not received them for close to on month, please contact your sales representative.

Solution:
Will be added to the next release.
 

Build 1021

AddressCheck Interface – Address does not code correctly when duplicate suite information is included in the address and suite fields.

Solution:
Fixed in Build 1027.

Build 1019

AddressCheck Interface – Certain LACSLink addresses are not converted correctly.

Solution:
Fixed in Build 1021.

Build 1017

AddressCheck Interface - Verifying certain company addresses in SQL Server stored procedures will cause a “Floating Point Error.”

Solution:
Fixed in Build 1019.

Work-Around:
Do not pass the company name into address object to avoid this crash.

AddressCheck Interface – GetCassForm method returns jumbled html string if called more than once.

Solution:
Fixed in Build 1019.

AddressCheck Interface - Canadian Addresses with LVR or rural zip codes will code any city and state as correct.

Solution:
We are working with the Canadian Post Office to sort out how to verify LVR and rural zip codes as there are special rules that apply to them.

Build 676

AddressCheck Interface - Certain wild card searches result in only one city being returned when in fact more cities exist.

Solution
Fixed in Build 1017

Example:
Input
CITY: c*
STATE: CA

Output
C S U Dom Hls - There are 350 cities in CA starting in C.

ZipData Interface - The ComputeDistance & ComputeBearing methods will crash when non-numeric in any of the arguments.

Solution
Fixed in Build 1017

Build 613

Address Object experiencing memory leaks in a server environment.

Solution
Fixed in Build 676

Address Object experiencing memory leaks in a server environment

AddressCheck Interface

    1. County Highway
    2. Initialize method
    3. Cold Fusion

StreetData Interface

    1. Initialize method

ZipData Interface

    1. Initialize method
    2. ComputeDistance & ComputeBearing methods

 

“The format of the DPV Footnotes has been changed to reflect CASS rules as required by the USPS.

DPV
DPV Footnotes were previously returned with a space between each footnote. Per CASS rules the footnotes no longer have spaces between them. Each footnote is always two characters in length so interpretation of the footnotes should still be easily done.”

AddressCheck Interface

County Highway
Currently County Highway addresses without a range will cause the Address Object to produce a General Protection Fault (GPF.

• Fixed in Build 676

Initialize Method

Address Object will not initialize when the file name is included in the paths passed into the Initialize method.

• Fixed in Build 676

Cold Fusion Warning

The following methods originally added for Cold Fusion users were omitted in the new build of Address Object:

•SetPathToUSFiles
•SetPathToCanadaFiles
•SetPathToDPVFiles

• Fixed in Build 676

StreetData Interface

Initialize Method
Address Object will not initialize when the file name is included in the paths passed into the Initialize method.

• Fixed in Build 676

ZipData Interface

ComputeDistance Method
The ComputeDistance & ComputeBearing methods return 9999 & 999 respectively regardless of the input.

• Fixed in Build 676

Initialize Method
Address Object will not initialize when the file name is included in the paths passed into the Initialize method.

• Fixed in Build 676

How to Register the Address Object with Microsoft Transaction Server (MTS)

Solution:
When Melissa Data COM Objects are used on Microsoft IIS web sites they should be added to the Microsoft Transactions Service (MTS). Registering the COM Objects is fast and easy. In Windows 2000 you open the Components Services in the Administrative Tools menu. In Components Services go to:

Computers/My Computer/COM+ Applications/IIS Out-Of-Process Applications/Components

Right click on Components and select New then Component. Then click on the "Import components(s) that are already registered". From the list of components you should import:

 •AddressObject.AddressCheck
 •AddressObject.Parse
 •AddressObject.StreetData
 •AddressObject.ZipCodeData

Click Next and you are done.