Accent problem

I'm having a problem with character accentuation in SQL Server 2000.
The database was created with SQL_Latin1_General_CP850_CI_AI Collation and
table varchar fields are using the same collation.
The problem happens when I use characters with accentuation, database is not
saving the correct character value, I don't know if it is a client
configuration problem or a database configuration problem.
If I insert the character 'á', it is saving as '?'.
I think it is not a collate problem because I'm trying to select the field
using a different collate but the character still wrong.
select my_field collate SQL_Latin1_General_CP1_CS_AS
from my_table
I don't how to solve this problem, it's a collation problem? Client
configuration problem?
Some help will be usefull.
Thanks.
Its hard to say. There are some problems with some of the input mechanisms.
For instance if you input text files into a text or varchar column using the
ado stream object, they seem to go in as Unicode with an unknown code page.
Converting the text files to ANSI and then importing them seems to fix this
behavior.
It could also be related to the regional settings on the client computer.
Exactly how are you inputting these characters.
"Depaula" <Depaula@.discussions.microsoft.com> wrote in message
news:172EDC2E-1BEF-496A-AB27-529B0C1EF4D9@.microsoft.com...
> I'm having a problem with character accentuation in SQL Server 2000.
> The database was created with SQL_Latin1_General_CP850_CI_AI Collation and
> table varchar fields are using the same collation.
> The problem happens when I use characters with accentuation, database is
> not
> saving the correct character value, I don't know if it is a client
> configuration problem or a database configuration problem.
> If I insert the character 'á', it is saving as '?'.
> I think it is not a collate problem because I'm trying to select the field
> using a different collate but the character still wrong.
> select my_field collate SQL_Latin1_General_CP1_CS_AS
> from my_table
> I don't how to solve this problem, it's a collation problem? Client
> configuration problem?
> Some help will be usefull.
> Thanks.
|||I have an application that inserts data collected from users, it is very
curious because I have the same applications working in other databases and
it works right.
Only in this situation I have this problem and I don't know how to identify
where is the problem.
In first time I thought that problem was the database collation, but when I
select data using other collation the problem still happening.
** The text fields are varchar(254).
Thanks for help me.
"Hilary Cotter" wrote:

> Its hard to say. There are some problems with some of the input mechanisms.
> For instance if you input text files into a text or varchar column using the
> ado stream object, they seem to go in as Unicode with an unknown code page.
> Converting the text files to ANSI and then importing them seems to fix this
> behavior.
> It could also be related to the regional settings on the client computer.
> Exactly how are you inputting these characters.
>
> "Depaula" <Depaula@.discussions.microsoft.com> wrote in message
> news:172EDC2E-1BEF-496A-AB27-529B0C1EF4D9@.microsoft.com...
>
>
|||are the regional settings of both machines identical?
"Depaula" <Depaula@.discussions.microsoft.com> wrote in message
news:9615ED1B-EF46-4F3D-B491-BC9703A029D8@.microsoft.com...
> I have an application that inserts data collected from users, it is very
> curious because I have the same applications working in other databases
and
> it works right.
> Only in this situation I have this problem and I don't know how to
identify
> where is the problem.
> In first time I thought that problem was the database collation, but when
I[vbcol=seagreen]
> select data using other collation the problem still happening.
> ** The text fields are varchar(254).
> Thanks for help me.
>
> "Hilary Cotter" wrote:
mechanisms.[vbcol=seagreen]
the[vbcol=seagreen]
page.[vbcol=seagreen]
this[vbcol=seagreen]
computer.[vbcol=seagreen]
and[vbcol=seagreen]
is[vbcol=seagreen]
field[vbcol=seagreen]
|||Have you tested to define your column as unicode column : nvarchar and not
varchar ?
Phil.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:e50MWXisEHA.3572@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> are the regional settings of both machines identical?
> "Depaula" <Depaula@.discussions.microsoft.com> wrote in message
> news:9615ED1B-EF46-4F3D-B491-BC9703A029D8@.microsoft.com...
> and
> identify
when[vbcol=seagreen]
> I
> mechanisms.
using[vbcol=seagreen]
> the
> page.
> this
> computer.
Collation[vbcol=seagreen]
> and
database
> is
> field
>
|||Hi Philippe,
Hmm... You are correct as Depaula's first posting indicated that he was
using "...and table varchar fields are using the same collation" and not
nvarchar!
Regards,
John
"Philippe [MS]" <ptrotin@.online.microsoft.com> wrote in message
news:u9$oczWtEHA.1220@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Have you tested to define your column as unicode column : nvarchar and not
> varchar ?
> Phil.
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:e50MWXisEHA.3572@.tk2msftngp13.phx.gbl...
very[vbcol=seagreen]
databases[vbcol=seagreen]
> when
> using
code[vbcol=seagreen]
fix[vbcol=seagreen]
2000.[vbcol=seagreen]
> Collation
> database
the[vbcol=seagreen]
Client
>