Customer Service | Training | Contact Us
Welcome!
Login
Search Options   products areas display

Which products should be considered?

All Products

ArcCAD
ArcEditor
ArcExplorer
ArcGIS Engine
ArcGIS Explorer
ArcGIS Image Server
ArcGIS Mobile
ArcGIS Server
ArcIMS
ArcInfo Desktop
ArcInfo Workstation
ArcLogistics Route
ArcPad
ArcPad Application Builder
ArcReader
ArcSDE
ArcView
ArcView 3.x
ArcWeb Services APIs
ArcWeb Toolbar for ArcGIS
Atlas GIS
BusinessMap
BusinessMap Pro
GIS Portal Toolkit
Job Tracking for ArcGIS
Maplex
MapObjects -- Java
MapObjects -- Windows
MapObjects IMS
MapObjects LT
MapStudio
Military Overlay Editor
NetEngine
PC ARC/INFO & DAK
PLTS
RouteMap
RouteMap IMS
SDE
Tracking Server

    Remember these settings for each visit More info
You are here:

Technical Article   FAQ:  Why does the attribute table have Null or empty values after a join?

Article ID: 31122
Software:  ArcGIS - ArcEditor 9.0, 9.1, 9.2, 9.3 ArcGIS - ArcInfo 9.0, 9.1, 9.2, 9.3 ArcGIS - ArcView 9.0, 9.1, 9.2, 9.3
Platforms: N/A

Question

Why does the attribute table have Null or empty values after a join?

Answer

After performing a join between a feature class and a stand-alone table, such as dBASE IV, dBASE V, CSV, or PRN, the values in the fields from the joined table are empty or Null.

Null values can be the result of several factors:

-Values in the specified fields for the join do not match. Joins are also case sensitive. For example, 'NEW YORK' will not join with 'New York'. To convert string values to the proper case, please refer to the Technical Article in the Related Information section below.

-The name of the table or feature class, or field names in the table or feature class, include spaces or special characters. -show me-

Question
What characters should not be used in ArcGIS for field names and table names?
Answer
For ArcGIS to work with multiple data types, certain characters in field or table names are not supported. These characters are spaces, hyphens such as 'x-coord', brackets, and other special characters. The above limits are imposed so that ArcGIS is able to function with the maximum amount of data types.

Eliminate anything that is not an alphanumeric character or an underscore. Do not start field or table names with an underscore or a number. Also, it is necessary to edit the field names in delimited text files to remove unsupported characters before using them.

The limit for the length of field and table names depends on the underlying database management system (DBMS). Consult the DBMS documentation for information on the limits for a particular DBMS. A dBASE field name can be up to 10 characters long, and there is no limit on the length of the table name. For coverages, use up to 16 letters or numbers. Coverage item or field names must begin with a letter, and cannot contain spaces.


-The table is stored in an Microsoft Access database that is not a personal geodatabase. -show me-

Summary
Neither adding a Microsoft Access table directly into ArcMap nor opening and modifying a Personal Geodatabase in Microsoft Access is supported by ESRI because they can damage the Access database. Instructions provided describe how to use Microsoft Access tables in ArcGIS via an OLE DB connection.

 Even though Microsoft Access Databases and ESRI's Personal Geodatabases are both built on the MDB file format, they should not be opened through their non-native software.
Procedure
Use the following procedure to create an OLE DB connection to the Access Database:

  1. In ArcCatalog, open the Database Connections folder, and double-click on 'Add OLE DB Connections' to open the Data Link Properties dialog box.
    -show me-
  2. Select the Microsoft Jet 4.0 OLE DB Provider and click Next.
    -show me-
  3. In section one, specify the database by navigating to it. If the database has a password, enter that information in section 2. Click on the Test Connection button to verify that the database can be connected to.
    -show me-
  4. To use the Access table through ArcMap, add the table through the OLE DB connection.
    -show me-

     Some users use Linked Tables in Access. These are not viewable through an OLE DB connection although Access Queries are. To use the Linked Table, create a Query in Access that references the Linked Table and connect to the linked table through the query in the OLE DB connection.

     There are a few limitations to be aware of when working with OLE DB connections. See the link in the Related Information section below for more information.


-The field names in the table are Microsoft Access reserved words. For a list of reserved words, see the Related Information section below.

Related Information


Created: 6/27/2006
Last Modified: 9/2/2008

This website's graphical display is now viewable only with W3C standards-compliant browsers, but the content is accessible to all browsers and Internet devices. View our supported browser matrix for more information on our website display.