Re: Codepage mismatch I think
From: Steve Kass (skass_at_drew.edu)
Date: 05/07/04
- Next message: Nikhil: "getting sum of units sold in preceeding weeks"
- Previous message: Vishal Parkar: "Re: Trucate Command"
- In reply to: johndotfoxley_at_laywheelerdotcom: "Codepage mismatch I think"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 07 May 2004 17:53:37 -0400
I'm not quite sure what your question is. Do you want to eliminate all
such characters from your database as a workaround for the problem with
your report writer? You certainly could do that:
update yourTable set
wineName = replace(replace(wineName, nchar(0x0107), N'c'),
nchar(0x0106), N'C')
This should be ok if the collation on the column is case-sensitive. If
it is not, you can get by with the lower-case substitution if you have
no capital C-acute letters, or you can try adding collate
your_base_collation_CS_AS to the parameters of the replace operation.
Unless you are using a code page the supports ć, you won't be able to
specify that character without the N prefix, and this is expected behavior.
If you can explain what you want to fix, feel free to ask another
question. It sounds to me like your report writer has a bug, and one
possibility is to address the issue with that vendor. By the way, the ć
character is used in some Eastern European languages, but is not in the
French or Italian alphabets, as far as I know.
Steve Kass
Drew University
johndotfoxley@laywheelerdotcom wrote:
>I am running SQL server 7 on an NT 4 server here in the UK
>which has a table containing French and Italian wine
>names. Most of the characters with accents are recognised
>fine but not the letter c with an acute (/) accent on it
>(the database records are populated by typing it out in
>Word and pasting it into the database table). If I use
>Query Analyser to then search for this character it does
>not find it unless I precede the search string with the
>letter N, as in like N'%c%' (where the c has an acute
>accent). Then it finds all occurences of this in the
>table. This has other implications with our report writer
>(compiles sql code) as the report fails when encountering
>a record with this character. I think it is a codepage mis-
>match somewhere but don't know what I need to do to fix it.
>
>
- Next message: Nikhil: "getting sum of units sold in preceeding weeks"
- Previous message: Vishal Parkar: "Re: Trucate Command"
- In reply to: johndotfoxley_at_laywheelerdotcom: "Codepage mismatch I think"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
