FAQ: Why does the attribute table have Null or empty values after a join?
Why does the attribute table have Null or empty values after a join?
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.
- The table is stored in an Microsoft Access database that is not a personal geodatabase. Refer to the article, How To: Use Microsoft Access tables in ArcGIS, 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.
- Join fields in the two tables are not the same data type.
- Fundamentals of adding and deleting fields, Field naming guidelines
- ArcGIS field data types
- FAQ: What characters should not be used in ArcGIS for field names and table names?
- How To: Use Microsoft Access tables in ArcGIS
- How To: Format a table in Microsoft Excel for use in ArcMap
- How To: Format a table in Microsoft Access for use in ArcMap
- How To: Convert a string to proper case in the ArcMap Field Calculator
- Microsoft Support - List of reserved words in Access 2002 and Access 2003