5 replies to this topic

[Hans van der Maarel]

So I have a Personal Geodatabase in ArcGIS 10.0 where I ended up with some attribute values that are almost the same, but not exactly. The difference is that there's one bunch of features saying "other" and another one saying "Other" (and they're actually subtly different, I messed up, I know that's bad...)

 

When I tried to select [value] = 'other' it returned both sets of features. Turns out that ArcGIS is only doing case insensitive selections in Personal Geodatabases. Seriously ESRI?

 

Funny enough the symbolisation is working case sensitive!

 

Any suggestion on how I can get around this?

[jrat]

Well, you could export your attribute table and use another editor that is case sensitive and replace one of your "o/Others" to something else. Then, join the table back to your FC and use the joined table to select the records to change, make your updates and trash the joined table.  You could use ObjectID as your join or create a temporary JoinID before you export the attribute table. You could use excel to find and replace all the 'others' to 'hey change this is Arcmap'.  excel has an option to match case while finding and replacing.

[Unit Seven]

Hey Hans,

 

ucase([VALUE]) = 'OTHER' should do what you are after. Or lcase([VALUE]) = 'other'.

 

Have to keep in mind Arc's selection all uses the SQL of the database being accessed—in the case of a personal it the same SQL as Access but if you were doing the same thing in an Oracle SDE database or File Geodatabase you need to change syntax accordingly.

[Hans van der Maarel]

Thanks for the suggestions. I ended up just running it through FME, doing an update on the table itself.

[rudy]

Hmmm. . . . not what I'm finding in 10.1 . . . seems to be case sensitive when going through Selection > Select by Attributes . . . .

[Hans van der Maarel]

Apparently it depends on the format your data is stored in (just like the use of ' vs " to identify text strings).