>>No you should set the content type on the ASP.NET application. It should be the Content-Type header. It's a global setting you can make in web.config.
>
>I always set pretty much everything in the application or the page itself. Is there an advantage to set that one in that particular place other than in the page?

Consistency. It's very easy to forget something in a page. If you set it in the .config it's one setting and you can change it globally. If you set it in the page you have to change it in every page as you have to do now if you want to switch to UTF 8.

>
>>There should really never be a reason to use anything but UTF-8 on a Web site.
>
>Yes, that resolved the issue.

Yes there really is no reason NOT to use UTF-8 that I can think of. Browsers default to it and UTF-8 can represent just about any character set. The only time you don't want to use it is if your HTTP client (like FoxPro maybe :-)) doesn't understand how to parse the UTF-8 natively. In that case a specific code page can be useful but even then it's usually easy enough to do the conversion (it's a pain to do manually in VFP unfortunately though).

+++ Rick ---