I was trying to determine the best way to standardize my attribute table.
I thought I would use a coded value domain but I am unable to do that without creating a subtype first. I don't understand this but figured I would just create a blank subtype to create the coded value domain. The trouble is that subtypes require a Long integer field which, when exported to a shapefile, are meaningless, just a number in a field.
Consequently, I decided to just create a new subtype properly. I attempted to delete the before mentioned domain and I get the error:
Failed to delete a domain from the database. The domain is used by an attribute rule.
I removed that "attribute rule" but it still will not delete.
The idea of subtypes and domains are a great idea but this locking problem and the subtype field requirement of being an integer rather than String is an issue for me.
For now I will just create the subtype and leave the domain.