Solved - See below - But those that use the server.transfer method may find it useful if the page contains non ascii characters. I am using ASP to generate a page from a database. I also use alaises on the site. So the following two utls are rendered by the same asp and should be identical. http://french-owners-direct.com/ShowProperty.asp?Property=1001 http://holiday-homes-france.com/ There appears to be one difference between them - (search for 'inclusive') There is a strange additional character in the second url that does not show up in the source. I am viewing them with IE7 & Firefox 2.0 both show the same results. The documents html both check out and they use the same stylesheet. I think it must be some document encoding problem - the second url is reached via a server transfer from the default asp page (index.asp) where I was very carefull not to output anything before the transfer. Any ideas anyone? David. FOUND IT. It would appear that even if you do not output anything (just asp code) before doing a server.transfer the codepage and charset are fixed at the moment of transfer. Fix: On the default page before the transfer added: <% Response.CodePage = 1252 Response.CharSet = "windows-1252" %> spent most of the day looking for that !.
