I don't see much use of SetOption('CaseSensitivity','on') but I sometimes see strings converted with UCase(). Now we know that KiX by default, is case insensitive and that it can be made case sensitive either with SetOption('CaseSensitivity','on') or by doubling up == on compares.
The question that begs to be asked is what would be considered "best practice"? If using string compares in a UDF, do you assume that 'CaseSensitivity' is 'off'; do you save/set/restore the SetOption; or do you convert all strings used in compares with UCase() or LCase()?
We know that other SetOption()s like 'Explicit' and 'NoVarsInStrings' can either break UDFs or if used carelessly in the UDF, cause calling scripts to fail.
I know that if we add this to the list, the UDF "Standards Police" may have a hayday pestering contributors but still, it deserves a mention.
_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.
