Matt [..] > The thought is that it is *not* being treated as if it were > HTML-encoded. It is being treated as a literal string. So, if > you type "&", you will get "&" just as if you had > typed "asdf" and got "asdf". To clarify: the input string *is* "ñ" the ouput string *is* "&#241;". What I require is that the input string *should be* "ñ" and the output string *should be* "ñ". Hence my belief that somewhere in the process of assigning the string value to a DropDownList item via a ListItem object, an HTML encoding method is being executed on the string. Apologies, either my powers of expression or my powers of comprehension have not been what they should have been over the past couple of days :) -- Chris Marsh Software Developer t: +44 20 8246 4804 x828 f: +44 20 8246 4808 e: chris at globet.com w: http://www.globet.com/ Any opinions expressed in this email are those of the individual and not necessarily the Company. This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential and privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system.