I just confirmed with tech support yet another behavior related to joins that worked at 10.0 and prior, but that broke with ArcMap 10.1 and later releases. You cannot join two data sources and then use simple Math in an SQL statement anymore. ArcMap crashes. So, for example, if you join a summary table on a field you cannot do the following selection anymore without crashing ArcMap:
JoinedTable.Frequency > 1 AND JoinedTable.Sum_Shape_Area < OriginalTable.Shape_Area + .001
The workaround I am using for the above selection is to create a new double field on the original table and use the Field Calculator to calculate [Shape_Area] + .001 into it and then changing the selection to JoinedTable.Frequency > 1 AND JoinedTable.Sum_Shape_Area < OriginalTable.Shape_Area. The math must be done by the field calculator, because using the above math in SQL crashes ArcMap on a duplicate of the Shape_Area values in a double field as much as it crashes when using the Shape_Area field. This behavior applies to all math operators.
I was a little frustrated that I had to explicitly ask for a NIM to be logged rather than just letting this be dismissed as an undocumented "known limitation". If replacing working behaviors with ArcMap crashes doesn't constitute a bug, I don't know what does. If they won't restore the behavior they at least need to stop it from crashing ArcMap and document that these SQL expressions are only supported for unjoined data sources.
Other less dramatic, but nonetheless very annoying broken behaviors related to joins that appeared at 10.1 include:
1. Feature selections and highlights in a joined table view no longer refreshes on a map without explicitly using the Refresh command, and once that behavior starts it cannot be stopped even after the join is broken. ArcMap must be closed and reopened to make selections and highlights appear correctly for the original unjoined data source.
2. The CAST SQL operator throws an error while tables are joined, forcing me to use the Field Calculator again to transfer data from the joined table to the original table in order to do the SQL on an unjoined table.
These behaviors are known to occur with file geodatabase data sources, which is virtually all I use, but they may apply to other data sources as well.
Anyway there may be other join behaviors that broke with the release of 10.1 that still are not fixed. If I recall any others I will add them to this post. Feel free to use this thread to list other broken behaviors related to joins that you are encountering in the latest releases. I would like to hear about them, since I use joins a lot.
JoinedTable.Frequency > 1 AND JoinedTable.Sum_Shape_Area < OriginalTable.Shape_Area + .001
The workaround I am using for the above selection is to create a new double field on the original table and use the Field Calculator to calculate [Shape_Area] + .001 into it and then changing the selection to JoinedTable.Frequency > 1 AND JoinedTable.Sum_Shape_Area < OriginalTable.Shape_Area. The math must be done by the field calculator, because using the above math in SQL crashes ArcMap on a duplicate of the Shape_Area values in a double field as much as it crashes when using the Shape_Area field. This behavior applies to all math operators.
I was a little frustrated that I had to explicitly ask for a NIM to be logged rather than just letting this be dismissed as an undocumented "known limitation". If replacing working behaviors with ArcMap crashes doesn't constitute a bug, I don't know what does. If they won't restore the behavior they at least need to stop it from crashing ArcMap and document that these SQL expressions are only supported for unjoined data sources.
Other less dramatic, but nonetheless very annoying broken behaviors related to joins that appeared at 10.1 include:
1. Feature selections and highlights in a joined table view no longer refreshes on a map without explicitly using the Refresh command, and once that behavior starts it cannot be stopped even after the join is broken. ArcMap must be closed and reopened to make selections and highlights appear correctly for the original unjoined data source.
2. The CAST SQL operator throws an error while tables are joined, forcing me to use the Field Calculator again to transfer data from the joined table to the original table in order to do the SQL on an unjoined table.
These behaviors are known to occur with file geodatabase data sources, which is virtually all I use, but they may apply to other data sources as well.
Anyway there may be other join behaviors that broke with the release of 10.1 that still are not fixed. If I recall any others I will add them to this post. Feel free to use this thread to list other broken behaviors related to joins that you are encountering in the latest releases. I would like to hear about them, since I use joins a lot.