Garry In my daily work in a credit database I sometimes have mangled business names or addresses that are too ... shall we say, beyond help ... to be properly handled by the built-in name and address rule system, so I will have to go into the class that controls that file format or specific data contributor to handle it. The method where that happens is downstream from a very basic "remove runs of spaces and upper case everything" operation, but I am usually pasting the mangled info directly from a submitted data file that is in mixed case. I will then highlight the quoted string and use Visual Studio's keyboard shortcut to upper-case it so that I can do a simple and fast == comparison in the code.
Of course C# is case-sensitive, unlike Objo Basic, so ... if I were doing this in Objo Basic since by default it compares strings case-insensitive, I wouldn't have to bother, yet I still probably would just for code consistency and clarity. That would also allow me to do a case-sensitive test even though it's upper case text -- that would probably be just a hair faster since it doesn't have to account for potential lower case characters being present. (Because of the variety of content we get, everything is "ASCII-fied" and upper cased internally, and any unusual punctuation, weird branding capitalization or needed accenting is applied separately in a display version of the name).