NIM044921 for ArcGIS for Desktop

Bug ID Number	NIM044921
Submitted	April 30, 2009
Last Modified	June 5, 2024
Applies to	ArcGIS for Desktop
Version found	9.3
Operating System	Windows OS
Operating System Version	XP
Status	Will Not Be Addressed

Additional Information

No Public Explanation

Workaround

As a general rule, users should not base joins on doubles in File or Personal geodatabase as they are floating point. What you see in the table is an approximation of what’s on disk in binary. It may work, it may not work. There are various factors that will increase the likely hood of there being no match. Alternative workflows:• Base your join on text or integer fields• SQL Server (SDE) and SQL Server Express (available with Desktop – no SDE required) support fixed point (as opposed to floating point) number fields. That is, you can specify a scale and precision. This will allow joins on doubles to work.• I also got it to work in file or personal using the following workflow. As stated above, joins on doubles may or may not work. So, if you use this workflow, you will have to check the join results to make sure everything matched.• I trimmed the double values to just have three decimal places. Since the numbers are distances, I didn’t think this was a problem.o If I then perform the join with no attribute index present, I get 100% match. So, remove the attribute index from the feature class or table in the feature class properties in ArcCatalog. Also, when prompted to create an index when joining, select NO.o If I then perform the join and select the option to keep only matching records, I also get 100% match, with or without an attribute index present.