Address Object Build History
Build 1895 Released 12/11
- INTERFACE CHANGES
- FUNCTIONALITY CHANGES
- Various soundexing improvements to improve address coding quality for middle to poor quality addresses
- Fixed bug with Non-USPS addresses and Disable Address Swapping in the COM Object.
- Fixed a bug with the USPS CASS form total records number including Canadian records.
- Fixed a bug with incorrect LOT numbers for UNIX platforms.
- DATA FILE CHANGES
Build 1876 Released 010/11
- INTERFACE CHANGES
- Added new result code AS03 - Non-USPS Address.
- New StandardizationType property which will allow you to choose the format of the output address. The possible values are
ShortFormat (St), LongFormat (Street), or AutoFormat. Please see the manual for more details.
- New AddressKey property added to Address Object. This key is returned after verification of an addressed and will used as
input to other services and objects like Geocoding and Delivery Indicator.
- FUNCTIONALITY CHANGES
- Address Object introduced DeliveryPlus. We have added up to 5 million Non-USPS addresses. These are real physical addresses that are not serviced by the USPS but may be deliverable by a third party carrier like UPS or FedEx. Please see the manual for details on the new result code, AS03.
- Fixed a bug that crashed Address Object when an invalid LastLine of over 200 characters was entered.
- Address Object AddressCheck interface now supports SQL Server extended stored procedures. Please look in the interfaces/sql directory for samples and instructions.
- Several code optimizations to improve memory handling within Address Object were made.
- Fixed a bug where dual Canadian addresses entered resulted in some data being lost during verification.
- Fixed misc. bugs.
- DATA FILE CHANGES
- Non-USPS address data added.
- GLOBAL CHANGES
- --NEW LICENSING MECHANISM--
Melissa Data is introducing a new License mechanism. Instead of individual Licenses to each product, we can now issue one
License to enable every object you are using. Additionally, this License key can be set as a environment variable (MD_LICENSE).
This way, licenses can be changes or swapped out without recompiling your application. Of course, the current method of setting
your license string will still work. Please reference the documentation under SetLicenseString for more details. A FAQ is also
available here: http://www.melissadata.com/tech/set-environment-variable.htm
Build 1816 Released 07/11
- INTERFACE CHANGES
- Added new result code AC14 - Suite range changed
- FUNCTIONALITY CHANGES
- Address Object is compliant with USPS Cycle N changes. SuiteLink add-on is now required to generate a CASS form (SetCassEnable(1)).
- Suite changes for alias, Suitelink, and AddressPlus addresses will now also trigger suite change codes (AC13 and AC14).
- Various bug fixes.
- Fixed a bug that caused limited suggestions to be generated by FindSuggestion()
- Urbanizations in the Address2 field will now be removed from Address2 and moved into the Urbanization field.
- DATA FILE CHANGES
- mdRBDI.dat file updated to improve accuracy.
- Global Changes
- PRESORT REMOVED FROM DATA QUALITY SUITE
- Presort Object has been removed from the Data Quality Suite DVD and will now reside on its own disc.
- CANADIAN DATA FILE NOW INCLUDED ON THE DISC
- The Canadian data file, previously only available as a download, will now be installed with the DQ Suite disc. Additionally, the expiration
for the Canadian file has been extended to 105 days, similar to the US data files.
- AUTOMATED DOWNLOAD SCRIPTS ADDED TO THE EXTRAS FOLDER
- New scripts for automating the download and update procedure for Address, Name, Phone, Email, and Geocoder objects are now located in the extras
directory. Currently, they are only available for Windows but a Linux version is in the works. They are not supported and we recommend you go through
them to understand how and when to use them.
- WINDOWS SETUP NO LONGER AUTOMATICALLY INSTALLS ADOBE READER
- Adobe Reader is available in the extras folder but the windows setup.exe will no longer automatically install it if it is currently missing.
This was done to make automating the install easier.
Build 1766 Released 04/11
- INTERFACE CHANGES
- Street Data has added a new DeliveryInstallation field. This field contains Canadian delivery installations and will not return any data for US street data searches.
- FUNCTIONALITY CHANGES
- MSA and PMSA fields will stop returning data since they have been deprecated by the Census Bureau for over 10 years and will
now return an empty string. Please contact your sales representative if you still require this data. It can be made available as a file download.
- Minor address correction issues for Canadian fixed.
- Minor issue regarding country code fixed.
Build 1730 Released 02/11
- New Features
- New Result Codes
A number of new Result codes are now available. Please
reference the Address Object manual for these new
Results codes and details for each.
- Fix country code handling
Address Object will now label an address as foreign is
it has a legitimate country code that is not "US" or
"CA".
- Change in SOA form
The old Canada Post SOA (Statement of Accuracy) form has
been changed. Canada Post no longer allows 3rd party
tool providers to be SERP certified, so Address Object
cannot produce official SOA forms anymore. Calling
GetSOAForm() or SaveSOAForm() will now return a general
Summary of Addresses form.
- FindSuggestion Changes
Implemented a time limit of FinSuggestion() and
FindSuggestionNext(). Will also only return suggestion
for AE02, AE03, and AE05 errors.
- Congressional file updated
110th.dbf has been updated to Congress.dbf and contains
the 112th congress information.
- Canadian StreetData searches now fully supported
FindStreet searches for Canada are now fully supported.
Search for PO Box, CP, or RR will now return Canadian
data.
Build 1663 Released 09/10
- New Features
- New LACSLink and SuiteLink data files
LACSLink®
and SuiteLinkTM datafiles for Address Object have
been merged into one file each namely: mdLacs.dat,
and mdSuiteLink.dat. To leverage the enhanced
performance and stability this affords, the Address
Object library will need to be updated when
installing these new data files. This build requires
the use of these new files. It cannot use the older
format LACSLink or SuiteLink data files.
- Updated CASS form template.
- Bug Fixes
- Fix some
inconsistent address results across different
platforms.
- Fix issue of truncating Canadian address
ranges at 6 digits.
- Fixed issue of swapped suffix and street
name for a certain address.
- Improved tie-breaking feature for Canadian
addresses with multiple possible matches.
- Fixed return value for InitializeErrorString
and InitializeDataFiles for a certain situation
where data files are not present.
- Fixed the issue of changing the zip format
for Canadian addresses that do not code.
- Fixed the issue of not being able to pass in
the ZipCodeOnly parameter in FindStreet using
SQL Server T-SQL.
- Made a number of fixes to FindSuggestion
function to improve the quality of suggested
results.
Build 1609 Released 06/10
- New Functionality
- New Suggestion Feature
Interface Changes: FindSuggestion() and
FindSuggestionNext() methods added to AddressCheck
Details: This new feature allows you to find
alternative suggested addresses if an input address
does not validate. If you received an error code for
the address:
if(FindSuggestion() == 1)
{ Display address output properties for first
suggestion;}
while(FindSuggestionNext() == 1)
{ Display address output properties for next
suggestion;}
Please reference the manual for details.
- New Canadian Engine
Interface Changes: ParsedRouteService,
ParsedLockBox, and ParsedDeliveryInstallation
properties added to AddressCheck
Details: We have a new Canadian verification
engine that has fixed many of the issues we have had
with our previous engine. Additionally, we have
added ParsedRouteService, ParsedLockBox, and
ParsedDeliveryInstallation properties for parsed
components of an Canadian address. These components
only apply to Canadian addresses.
- Canadian Support for the Parse Interface
Interface Changes: RouteService, LockBox, and
DeliveryInstallation properties and ParseCanadian()
method added to Parse.
Details: We have added support for Canadian
addresses to our Parse Interface. To use, pass a
Canadian address into ParseCanadian(). RouteService,
LockBox, and DeliveryInstallation properties were
added to hold canadian only address components.
Please see manual for more details.
- Canadian Support for ZipData Interface
Interface Changes: None
Details: Address Object ZipData Interface now
supports Canadian postal codes in the FindZip,
FindCityInState, and FindZipInCity searches.
- Canadian Support for StreetData Interface
Interface Changes: None
Details: Address Object StreetData Interface
now supports Canadian streets in the FindStreet
search.
- Bug Fixes
- A crash when
calling RBDI without calling any other property
first has been fixed.
- Fixed a bug in which the wrong city is
returned if both the company and the address
line contained company information.
- Fixed a bug where the same PO Box was
returned in Address1 and Address2 if two
addresses were combined into one line on input.
- Fixed a bug where CALI was not being
recognized as California in the state field.
- Fixed a bug where an address with a
numerical company name and an address with no
range was not validated.
Build 1567 Released 03/10
- Bug Fix
- Fixed a bug in which the SetPathToCanadaFiles() method did not work in T-SQL when using a char instead of a varchar for the path.
- Fixed a bug with a few rare addresses where the pre-direction was being changed incorrectly.
- Changed Functionality
- Correction of incorrectly placed PMB's
: Allowed Address Object to recognize an unnecessary suite as a private mailbox at a CMRA.
- In compliance with CASS Cycle M changes, if a street address and a PO Box are both entered in the Address line, the street address now takes precedence and the PO Box is moved to Address2.
- Street Match, Vacant, Alternate Delivery, and DPV Lookout Result codes added: Although not officially released, Result codes were available for use in the previous build. This build adds new Result codes for AS02: Address matched to street but suite invalid, AS16: Address vacant, AS17: Alternate Delivery AS18: Artifically generated address detected. Please see manual for more details.
- State field allowable input expanded
: The state input field can now take the full state name as well as slightly mispelled state names. Previously, only the first two letters in the state field were used.
- New Functionality
- Interface changes:
New Results property added: Address Object introduces Result Codes. Combined into a comma delimited string, Results contains all the status and errors into one location instead of in 3 separate properties (Status, ErrorCode, ErrorString). Also, new functionality has been added using Results.
Build 1473 Released 12/09
Bug Fix
- ProgramStatus return from InitializeDataFiles() fixed
- Fixed a bug where InitializeDataFiles() returned integers beyond the range of the ProgramStatus enumeration.
Build 1472 Released 10/09
Bug Fix
Fixed a bug in AIX and HP-UX where a very small percentage of addresses crashed when an address swap occurred.
Build 1451 Released 08/09
- Address Object has been compiled in Visual Studio 2008. Running
setup.exe will ensure the necessary libraries are installed.
However, if you are installing the objects manually, you may need to
install Visual Studio 2008 C++ x86 redistributable, which can be
found in extras\redist.
- This update of Address Object has been certified with the new CASS
cycle M, which begins on July 31st, 2009.
Build 1431 Released 06/09
This updates adds three new data file sets:
-
SuiteLink: A new postal requirement for Cycle M CASS™ (2009)
processing. This dataset allows Address Object to append missing
suite numbers when some business names and address are entered.
CASS™ now requires DPV, LACSLink and SuiteLink. A new property
PathToSuiteLinkDataFiles has been added to initialize this data
set.
- SuiteFinder: Compliment data set to SuiteLink. This dataset
allows Address Object to append missing suite numbers to
residential addresses when a last name is provided. A new
property PathToSuiteFinderDataFiles has been added to initialize
this data set.
- eLot: Allows Address Object to return Lot order and Lot number
sequence used with bulk mail toolkits such as Presort Object to
qualify for carrier route line of travel rates. To use, place
this data set in the same directory as your DPV data files.
This update uses the new Canadian data set. A new Canadian data
file named mdCanada3.db has been distributed with the Canadian
update since May 2009. This update will require that data file
instead of the previous set of data files (mdCanada.db,
IndxKey1.txt, IndxDic1.txt). This update contains significant speed
increases for Canadian address lookups, specifically with missing
components such as Postal Codes.
Build 1395 Released 04/09
The Address Object now is now using a new Parsing Technology. This
new Parser was designed to improve the number of imperfect addresses
that the Address Object is able to verify. With the new Address
Object Parser, several Addresses which were not recognized before,
are now being verified properly.
Build 1352 Released 10/08
- Fixed the following issues:
- Miscellaneous Casing issues.
-
Fixed a Canadian issue where ParsedAddressRange sometimes return
99999999 if a range was not present in the address.
-
Fixed a crash in the Parse Interface if the Address1 line is
greater than 200 characters.
- Fixed a crash on a few platforms when an address contained
non-standard characters.
- Verification of Canadian addresses without postal codes has been
optimized.
- Added features:
- A new Error Code of "F" and corresponding Error String of
"Non-Canadian Postal Code" has been added. You will get this
error if you have only the Canadian Data Files initialized and
try to verify an address with a postal code that is not
Canadian.
-
A new property called UseUSPSPreferredCityNames has been
added. Here are the possible input values and results for this new property.
- Does not turn this new feature on and Address Object will behave exactly as it did before.
- Will always return the Preferred City Name for the
input address if the address can be verified.
(Using this new feature will convert all vanity city names
to the preferred city name. You must set this property
before initialization.)
- Deprecated Builds:
- The old-style AMS interface libAddr.so.
- The Solaris (compat) folder with the Solaris 7 GNU binary.
Replaced with Solaris 8.
- The Linux (compat) binary for GCC 2.9. Replaced with GCC 3.2.
- Added Platforms:
AIX™ versions: 5.2,5.3. POWER, rs/6000, PPC, 32 Bit, (GCC
3.4.x)
Build 1262 Released 02/08
Build 1191 Released 9/07
Fixed the following issues:
- A crash when calling GetMSA() under certain situations
- Canadian addresses that do not have a valid postal code but valid city/state did not code correctly.
- A few addresses where the only incorrect information was the state, Address Object will code the address as correct but does not correct the state.
Build 1166 Released 7/07
- Added Features:
- Added property CASSEnable (Windows), and method
SetCASSEnable (Unix)
- Various CASS Cycle L changes.
- The new CASS Cycle L mandates that DPV be required for USPS CASS
mailings. So, CASSEnable has been added to fulfill this requirement.
With CASSEnable set to true, must use DPV to verify US addresses. If
an address does not DPV code, you will not get a plus4 back. With
CASSEnable set to false (default), DPV is still optional but you
will not be able to generate a CASS form. Also, addresses that do
not DPV code but zip+4 codes will still return a plus4. Please
reference the Address Object manual for more details.
Build 1150 Released 6/07
Fixed the following issues:
- Fixed an issue with
JavaScript and the loading of the DPV data files.
Fixed the casing of several Canadian Addresses.
Fixed a crash when trying to verify a Canadian postal code with
over 50 characters.
Build 1115 Released 4/07
Added Features:
Added the following properties and methods to Address Object to
support the addition of SOA forms (Statement of Accuracy) for
Canadian Address verification.
//** Canadian Date Methods **//
GetCanadianDatabaseDate
GetCanadianExpirationDate
- //** Canadian SOA Form methods **//
GetFormSOA
SaveFormSOA
ResetFormSOA
SetSOACustomerInfo
SetSOACPCNumber
- //** Canadian SOA Form properties **//
SOACustomerInfo
SOACPCNumber
SOATotalRecords
SOAAAPercentage
SOAAAExpiryDate
SOASoftwareInfo
SOAErrorString
Recompilation of the application is necessary only if you choose to
use these properties.
Build 1098 Released 2/07
Fixed several issues with Canadian Addresses.
Build 1091 Released 12/06
Added Features:
A new version of the Canada Add-on has been added to the object.
Address object now uses faster and more stable cross platform code
instead of using an mdb file. Address Object for UNIX (Linux,
Solaris, AIX, HPUX) now has Canadian support. To upgrade to the new
Canadian Add-on: download the new Canadian data files and upgrade
Address Object to this new version. All code in your application
stays the same but the new object will not work with the old
Canada.mdb file. If you currently subscribe to the Canadian Add-on,
please contact your sales representative to get the new data files.
-
The DPV data files have been restructured and now consist of six
files instead of 107. It still behaves exactly the same as it did
before but users should erase the old DPV files when installed DPV.
Build 1034 Released 8/06
Fixed the Following Issues:
Miscellaneous bug fixes.
Build 1027 Released 6/06
Fixed the Following Issues:
Made miscellaneous speed improvements to the DPV add-on.
Build 1025 Released 5/06
Fixed the Following Issues:
Fixed a bug that occurred when duplicated suite
information is included in the address and suite fields.
Build 1021 Released 4/05
Fixed the Following Issues:
- Fixed the core dump crash with the GNU C++ 3.3 Solaris
object (in the compat folder).
- Fixed a segmentation fault with the Linux and Solaris objects
when certain addresses were entered in the Address2 field.
- Fixed a bug where LACSLink failed to convert certain rural
route addresses to the new 911 form of the address.
|