I'm having trouble figuring out why apparently a table from a file geodatabase isn't interpreted correctly. These are some of the fields as they should show up in the table view:
However, the table view doesn't show the right headers and also mixes up values:
In that image,
- the column marked with "1" should be named "idia_r"
- the column marked with "2" should be named "flow_r"
- the column marked with "3" is fine.
When I join this table to a line feature class (also from a file geodatabase, but a different one), I get the same mixup in column names. Again, the property window shows the right attributes:
Why does this happen and how can I fix it?