Differences

This shows you the differences between two versions of the page.

--- dynamiczip:glossary:zip_address_import_source_file [2015/05/18 21:48] – conni
+++ dynamiczip:glossary:zip_address_import_source_file [2018/09/25 22:06] (current) – conni
@@ Line 3: / Line 3: @@
 A Zip Address Import Source file is the ASCII file from which you will be [[dynamiczip:features:import:Import Zip Addresses|Importing Zip Addresses]]. The ASCII file can be comma or tab-delimited, or fixed position.
-The Zip.txt file included in the [[dynamiczip:glossary:rate_and_boundary_database|Rate & Boundary Database]] is an example of this type of file.
+The Zip.txt file included in the [[dynamiczip:glossary:zipsales_database|ZIPsales Database]] is an example of this type of file.
 **Required fields are:**
@@ Line 21: / Line 21: @@
 Geocode is used to uniquely identify the combination of city, county and state. The primary key on the [[dynamiczip:tables:DZ Zip Address table]] is Geocode and ZIP Code. As a result, if geocode is blank, there can only be one city per ZIP Code. If that city name being imported is the USPS city, this should not be a problem. However this could be a problem if your source file contains actual city names as opposed to the [[dynamiczip:glossary:usps_city_name|USPS Preferred City Name]].
-If your import source file does not contain geocodes and you want more than one city name per ZIP code, you can modify the file to add geocodes. Here is one way you can create your own geocodes:
+If your import source file does not contain geocodes and you want more than one city name per ZIP Code, you can modify the file to add geocodes. Here is one way you can create your own geocodes:
   - Open your import source file with Excel being sure to flag the ZIP Code column as text (while opening) so that the leading zeros will not be dropped.
@@ Line 31: / Line 31: @@
   - Save the Excel file. (If you save it as an Excel spreadsheet, you will be able to open it again easily. However you must also save it as a Text file (tab or comma delimited) or as Formatted Text (space delimited) so that you can [[dynamiczip:features:import:Import Zip Addresses|import]] the results.
-When importing from a source other than the [[dynamiczip:glossary:rate_and_boundary_database|Rate & Boundary Database]] existing but obsolete ZIP Codes are NOT purged from the [[dynamiczip:tables:DZ Zip Address table]] If you want to clean out obsolete ZIP Codes, you will need to do that with a SQL Query. Here is an example SQL Query to use for that purpose:
+When importing from a source other than the [[dynamiczip:glossary:zipsales_database|ZIPsales Database]] ZIP.txt file existing but obsolete ZIP Codes are NOT purged from the [[dynamiczip:tables:DZ Zip Address table]] If you want to clean out obsolete ZIP Codes, you will need to do that with a SQL Query. Here is an example SQL Query to use for that purpose:
 USE DYNAMICS
@@ Line 55: / Line 55: @@
 WHERE KDGeoCode = '' -- Assuming that you did not import geocodes
-Even when importing from a source other than the [[dynamiczip:glossary:rate_and_boundary_database|Rate & Boundary Database]] the DynamicZip setup option [[dynamiczip:windows:dz_naming_rules_window|Use Naming Rules for New Cities & Counties]] is effective. You should consider turning this option off while performing the [[dynamiczip:features:import:Import Zip Addresses|Zip Address Import]].
+Even when importing from a source other than the [[dynamiczip:glossary:zipsales_database|ZIPsales Database]] ZIP.txt file, the DynamicZip setup option [[dynamiczip:windows:dz_naming_rules_window|Use Naming Rules for New Cities & Counties]]((This feature was discontinued in Build 74)) is effective. You should consider turning this option off while performing the [[dynamiczip:features:import:Import Zip Addresses|Zip Address Import]].
 ----