Issues:Address Object - Revision history

Admin at 20:01, 11 March 2016

2016-03-11T20:01:04Z

← Older revision		Revision as of 20:01, 11 March 2016
Line 1:		Line 1:
			[[Address Object\|← Address Object]]
	{{CustomTOC}}		{{CustomTOC}}
	Address Object known issues.		Address Object known issues.

Admin at 16:31, 7 July 2014

2014-07-07T16:31:08Z

← Older revision		Revision as of 16:31, 7 July 2014
Line 22:		Line 22:

	:;Work-Around		:;Work-Around
	::Do not use the PathToLACSLinkDataFiles, PathToSuiteLinkDataFiles, and PathToSuiteFinderData add-ons~~. This will be fixed in the next future build~~.		::Do not use the PathToLACSLinkDataFiles, PathToSuiteLinkDataFiles, and PathToSuiteFinderData add-ons.

	==Build 1431==		==Build 1431==

Admin at 19:21, 2 August 2012

2012-08-02T19:21:11Z

← Older revision		Revision as of 19:21, 2 August 2012
Line 16:		Line 16:

	==Build 1609==		==Build 1609==
	''Released June 2010		''Released June 2010''

	;AddressCheck Interface:		;AddressCheck Interface:

Admin at 23:28, 31 July 2012

2012-07-31T23:28:17Z

← Older revision		Revision as of 23:28, 31 July 2012
Line 227:		Line 227:
	:*:Address Object will not initialize when the file name is included in the paths passed into the 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		::*Fixed in Build 676


			[[Category:Issues]]
			[[Category:Address Object]]

Admin at 23:27, 31 July 2012

2012-07-31T23:27:18Z

← Older revision		Revision as of 23:27, 31 July 2012
Line 7:		Line 7:
	;AddressCheck Interface		;AddressCheck Interface
	:Commercial Mail Receiving Agency addresses will not be flagged and recognized as a CMRA Address (AS10) for data files pushed out in February (02-2012) and March(03-2012). The USPS, beginning with the February release of the DPV® monthly data fulfillment, P.O. Box™ (PBSA) records were added to the CMRA table without partner notification. As a result, the file size of the CMRA (dph.hsc) table increased from 1 MB to 33 MB. This change has affected the Address Object lookups for CMRA addresses. The next build of Address Object will address and fix this issue. Meanwhile to fix this issue, please replace the dph.hsc files from February/March with the file from January (01-2012) by following the steps below:		:Commercial Mail Receiving Agency addresses will not be flagged and recognized as a CMRA Address (AS10) for data files pushed out in February (02-2012) and March(03-2012). The USPS, beginning with the February release of the DPV® monthly data fulfillment, P.O. Box™ (PBSA) records were added to the CMRA table without partner notification. As a result, the file size of the CMRA (dph.hsc) table increased from 1 MB to 33 MB. This change has affected the Address Object lookups for CMRA addresses. The next build of Address Object will address and fix this issue. Meanwhile to fix this issue, please replace the dph.hsc files from February/March with the file from January (01-2012) by following the steps below:


	#Download the January CMRA table (dph.hsc)		#Download the January CMRA table (dph.hsc)
Line 31:		Line 30:
	:String data stored in variant types are not being recognized in the Parse interface Parse() method and ZipData interface FindZipInCity() methods. For those methods, if you are using a scripting language that contains variant types (VBScript), passing in data of type variant will not work.		:String data stored in variant types are not being recognized in the Parse interface Parse() method and ZipData interface FindZipInCity() methods. For those methods, if you are using a scripting language that contains variant types (VBScript), passing in data of type variant will not work.

	Example:		:Example:
	<blockquote>		<blockquote>
	<pre>Dim datapath ‘Variant		<pre>Dim datapath ‘Variant

Admin at 23:25, 31 July 2012

2012-07-31T23:25:06Z

← Older revision		Revision as of 23:25, 31 July 2012
Line 141:		Line 141:
	*:GetCassForm method returns jumbled html string if called more than once.		*:GetCassForm method returns jumbled html string if called more than once.

	:*;Solution:		::;Solution:
	:*:Fixed in Build 1019.		:::Fixed in Build 1019.

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

	:*;Solution:		::;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.		:::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.


Line 156:		Line 156:
	*:Certain wild card searches result in only one city being returned when in fact more cities exist.		*:Certain wild card searches result in only one city being returned when in fact more cities exist.

	:*;Solution		::;Solution
	:*:Fixed in Build 1017		:::Fixed in Build 1017
	<blockquote>		<blockquote>
	Example:		Example:<br />
	Input		Input
	<pre>CITY: c*		<pre>CITY: c*
	STATE: CA</pre>		STATE: CA</pre>
	~~<br />~~
	Output		Output
	<pre>C S U Dom Hls - There are 350 cities in CA starting in C.</pre>		<pre>C S U Dom Hls - There are 350 cities in CA starting in C.</pre>
Line 171:		Line 170:
	*:The ComputeDistance & ComputeBearing methods will crash when non-numeric in any of the arguments.		*:The ComputeDistance & ComputeBearing methods will crash when non-numeric in any of the arguments.

	:*;Solution		::;Solution
	:*:Fixed in Build 1017		:::Fixed in Build 1017


Line 209:		Line 208:
	*Cold Fusion Warning		*Cold Fusion Warning
	*:The following methods originally added for Cold Fusion users were omitted in the new build of Address Object:		*:The following methods originally added for Cold Fusion users were omitted in the new build of Address Object:
	:*SetPathToUSFiles		::*SetPathToUSFiles
	:*SetPathToCanadaFiles		::*SetPathToCanadaFiles
	:*SetPathToDPVFiles		::*SetPathToDPVFiles
	<br />		<br />
	:*Fixed in Build 676		::*Fixed in Build 676


	*StreetData Interface		*StreetData Interface
Line 225:		Line 225:
	::*Fixed in Build 676		::*Fixed in Build 676

	**;Initialize Method		:*;Initialize Method
	**:Address Object will not initialize when the file name is included in the paths passed into the 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		::*Fixed in Build 676

Admin at 23:21, 31 July 2012

2012-07-31T23:21:33Z

← Older revision		Revision as of 23:21, 31 July 2012
Line 104:		Line 104:
	:GetCanadianExpirationDate()		:GetCanadianExpirationDate()

	*;Work-around:		:;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.		::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:		:;Solution:
	*:Will be added to the next release.		::Will be added to the next release.


Line 132:		Line 132:
	*:Verifying certain company addresses in SQL Server stored procedures will cause a “Floating Point Error.”		*:Verifying certain company addresses in SQL Server stored procedures will cause a “Floating Point Error.”

	**;Solution:		:*;Solution:
	**:Fixed in Build 1019.		:*:Fixed in Build 1019.

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

	*;AddressCheck Interface		*;AddressCheck Interface
	*:GetCassForm method returns jumbled html string if called more than once.		*:GetCassForm method returns jumbled html string if called more than once.

	**;Solution:		:*;Solution:
	**:Fixed in Build 1019.		:*:Fixed in Build 1019.

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

	**;Solution:		:*;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.		:*: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.


Line 156:		Line 156:
	*:Certain wild card searches result in only one city being returned when in fact more cities exist.		*:Certain wild card searches result in only one city being returned when in fact more cities exist.

	**;Solution		:*;Solution
	**:Fixed in Build 1017		:*:Fixed in Build 1017
	<blockquote>		<blockquote>
	Example:		Example:
	<pre>~~Input~~		Input
	CITY: c*		<pre>CITY: c*
	STATE: CA		STATE: CA</pre>
	<br />		<br />
	Output		Output
	C S U Dom Hls - There are 350 cities in CA starting in C.</pre>		<pre>C S U Dom Hls - There are 350 cities in CA starting in C.</pre>
	</blockquote>		</blockquote>

Line 171:		Line 171:
	*:The ComputeDistance & ComputeBearing methods will crash when non-numeric in any of the arguments.		*:The ComputeDistance & ComputeBearing methods will crash when non-numeric in any of the arguments.

	**;Solution		:*;Solution
	**:Fixed in Build 1017		:*:Fixed in Build 1017


	==Build 613==		==Build 613==
	*Address Object experiencing memory leaks in a server environment.		*Address Object experiencing memory leaks in a server environment.

	*;Solution		*;Solution
	*:Fixed in Build 676		:*Fixed in Build 676

			:*AddressCheck Interface
	*:~~Address Object experiencing memory leaks in a server environment~~
	**AddressCheck Interface
	::#County Highway		::#County Highway
	::#Initialize method		::#Initialize method
	::#Cold Fusion		::#Cold Fusion

	**StreetData Interface		:*StreetData Interface
	::#Initialize method		::#Initialize method

	**ZipData Interface		:*ZipData Interface
	::#Initialize method		::#Initialize method
	::#ComputeDistance & ComputeBearing methods		::#ComputeDistance & ComputeBearing methods
Line 206:		Line 203:
	:*Fixed in Build 676		:*Fixed in Build 676

	Initialize Method		*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

	Address Object ~~will not initialize when the file name is included~~ in ~~the paths passed into the Initialize method.~~		*Cold Fusion Warning
			*:The following methods originally added for Cold Fusion users were omitted in the new build of Address Object:
			:*SetPathToUSFiles
			:*SetPathToCanadaFiles
			:*SetPathToDPVFiles
			<br />
			:*Fixed in Build 676

	~~• Fixed in Build 676~~		*StreetData Interface
			*;Initialize Method
	~~Cold Fusion Warning~~		*:Address Object will not initialize when the file name is included in the paths passed into the Initialize method.
			:*Fixed in Build 676
	~~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		*ZipData Interface
	~~Address Object will not initialize when~~ the ~~file name is included~~ in ~~the paths passed into the Initialize method.~~		**;ComputeDistance Method
			**:The ComputeDistance & ComputeBearing methods return 9999 & 999 respectively regardless of the input.
			::*Fixed in Build 676

	• 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

Admin at 23:13, 31 July 2012

2012-07-31T23:13:39Z

← Older revision		Revision as of 23:13, 31 July 2012
Line 61:		Line 61:
	*:A few Canadian Addresses are not returning a status code:		*:A few Canadian Addresses are not returning a status code:

	:;Solution:		::;Solution:
	::This will be fixed in the next release.		:::This will be fixed in the next release.

	*;AddressCheck Interface		*;AddressCheck Interface
	*:If a valid address is entered in the Company field and invalid characters in the Address field, Address Object will swap them and code the valid address but the company name is lost.		*:If a valid address is entered in the Company field and invalid characters in the Address field, Address Object will swap them and code the valid address but the company name is lost.

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

	*;AddressCheck Interface		*;AddressCheck Interface
	*:If an invalid zip code is used and the city field is left blank, Address object cannot code the address because it doesn’t have enough information but it will fill in the city field with the first alphabetical city in the input state.		*:If an invalid zip code is used and the city field is left blank, Address object cannot code the address because it doesn’t have enough information but it will fill in the city field with the first alphabetical city in the input state.

	:;Work-Around:		::;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.		:::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.

Admin at 23:12, 31 July 2012

2012-07-31T23:12:29Z

← Older revision		Revision as of 23:12, 31 July 2012
Line 132:		Line 132:
	*:Verifying certain company addresses in SQL Server stored procedures will cause a “Floating Point Error.”		*:Verifying certain company addresses in SQL Server stored procedures will cause a “Floating Point Error.”

	:;Solution:		**;Solution:
	::Fixed in Build 1019.		**:Fixed in Build 1019.

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

	*;AddressCheck Interface		*;AddressCheck Interface
	*:GetCassForm method returns jumbled html string if called more than once.		*:GetCassForm method returns jumbled html string if called more than once.

	:;Solution:		**;Solution:
	::Fixed in Build 1019.		**:Fixed in Build 1019.

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

	:;Solution:		**;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.		**: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==		==Build 676==

	AddressCheck Interface - Certain wild card searches result in only one city being returned when in fact more cities exist.		*;AddressCheck Interface
			*:Certain wild card searches result in only one city being returned when in fact more cities exist.
	~~Solution~~
	~~Fixed in Build 1017~~

			**;Solution
			**:Fixed in Build 1017
			<blockquote>
	Example:		Example:
	Input		<pre>Input
	CITY: c*		CITY: c*
	STATE: CA		STATE: CA
			<br />
	Output		Output
	C S U Dom Hls - There are 350 cities in CA starting in C.		C S U Dom Hls - There are 350 cities in CA starting in C.</pre>
			</blockquote>

	~~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~~		*;ZipData Interface
	~~Fixed~~ in ~~Build 676~~		*:The ComputeDistance & ComputeBearing methods will crash when non-numeric in any of the arguments.

	~~Address Object experiencing memory leaks~~ in ~~a server environment~~		**;Solution
			**:Fixed in Build 1017

	~~AddressCheck Interface~~

	~~1. County Highway~~		==Build 613==
	~~2. Initialize method~~		*Address Object experiencing memory leaks in a server environment.
	3. ~~Cold Fusion~~

	~~StreetData Interface~~		*;Solution
			*:Fixed in Build 676

	~~1. Initialize method~~

	~~ZipData~~ Interface		*:Address Object experiencing memory leaks in a server environment
			**AddressCheck Interface
			::#County Highway
			::#Initialize method
			::#Cold Fusion

	1. Initialize method		**StreetData Interface
	~~2. ComputeDistance & ComputeBearing methods~~		::#Initialize method

			**ZipData Interface
			::#Initialize method
			::#ComputeDistance & ComputeBearing methods


	~~“The~~ format of the DPV Footnotes has been changed to reflect CASS rules as required by the USPS.		*The format of the DPV Footnotes has been changed to reflect CASS rules as required by the USPS.
			*;DPV
	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.”
	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		*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		Initialize Method

Admin at 23:06, 31 July 2012

2012-07-31T23:06:42Z

← Older revision		Revision as of 23:06, 31 July 2012
Line 41:		Line 41:
	::This will be fixed in the next release. Until then, you can use one of these two work-arounds.		::This will be fixed in the next release. Until then, you can use one of these two work-arounds.

	##Roll back to the previous object		:#Roll back to the previous object
	##Cast the Variant as a string. Example: parseObj.Initialize(CStr(datapath))		:#Cast the Variant as a string. Example: parseObj.Initialize(CStr(datapath))


Line 58:		Line 58:
	''Released September 2007''		''Released September 2007''

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

	:;Solution:		:;Solution:
	::This will be fixed in the next release.		::This will be fixed in the next release.

	;AddressCheck Interface		*;AddressCheck Interface
	:If a valid address is entered in the Company field and invalid characters in the Address field, Address Object will swap them and code the valid address but the company name is lost.		*:If a valid address is entered in the Company field and invalid characters in the Address field, Address Object will swap them and code the valid address but the company name is lost.

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

	;AddressCheck Interface		*;AddressCheck Interface
	:If an invalid zip code is used and the city field is left blank, Address object cannot code the address because it doesn’t have enough information but it will fill in the city field with the first alphabetical city in the input state.		*:If an invalid zip code is used and the city field is left blank, Address object cannot code the address because it doesn’t have enough information but it will fill in the city field with the first alphabetical city in the input state.

	:;Work-Around:		:;Work-Around:
Line 80:		Line 80:
	''Released July 2007''		''Released July 2007''

	AddressCheck Interface – Valid Canadian addresses that do not have a postal code are incorrectly verifying as an bad address. This only affect Canadian addresses that are street addresses and does not affect any US addresses or Canadian Rural Route, General Delivery, PO Box addresses.		;AddressCheck Interface
	Solution:		:Valid Canadian addresses that do not have a postal code are incorrectly verifying as an bad address. This only affect Canadian addresses that are street addresses and does not affect any US addresses or Canadian Rural Route, General Delivery, PO Box addresses.
	This has been fixed in the next release. Please download the latest version of Address Object on the main Address Object Support Page.
			:;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~~		==Build 1115==
			''Released April 2007''

	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.		;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:		:;Solution:
	The specific records have since been corrected and will be available in the next release.		::The specific records have since been corrected and will be available in the next release.


	Build 1091 Released ~~12/06~~		==Build 1091==
			''Released December 2006''

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

	Work-around:		*;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.		*: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:		*;Solution:
	Will be added to the next release.		*:Will be added to the next release.


	Build 1021		==Build 1021==
			;AddressCheck Interface
			:Address does not code correctly when duplicate suite information is included in the address and suite fields.

	~~AddressCheck Interface – Address does not code correctly when duplicate suite information is included~~ in ~~the address and suite fields~~.		:;Solution:
			::Fixed in Build 1027.

	~~Solution:~~
	~~Fixed in Build 1027.~~

	Build 1019		==Build 1019==

	AddressCheck Interface – Certain LACSLink addresses are not converted correctly.		;AddressCheck Interface
			:Certain LACSLink addresses are not converted correctly.

	Solution:		:;Solution:
	Fixed in Build 1021.		::Fixed in Build 1021.

	~~Build 1017~~

	AddressCheck Interface - Verifying certain company addresses in SQL Server stored procedures will cause a “Floating Point Error.”		==Build 1017==
			*;AddressCheck Interface
			*:Verifying certain company addresses in SQL Server stored procedures will cause a “Floating Point Error.”

	Solution:		:;Solution:
	Fixed in Build 1019.		::Fixed in Build 1019.

	Work-Around:		:;Work-Around:
	Do not pass the company name into address object to avoid this crash.		::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~~:		*;AddressCheck Interface
	~~Fixed in Build 1019~~.		*:GetCassForm method returns jumbled html string if called more than once.

	~~AddressCheck Interface - Canadian Addresses with LVR or rural zip codes will code any city and state as correct~~.		:;Solution:
			::Fixed in Build 1019.

	~~Solution~~:		*;AddressCheck Interface
	~~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~~.		*: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		==Build 676==

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