Re: Character Codepage

Most ODBC drivers can do codepage translation (with the right parameter, of
course) but this doesn't mean that a codepage translation will always be
successful at 100% because there are many incompatibilities between meany
codepages. You can make a call to the Windows API to determine the windows
code page of a running machine but if you have a translation problem, a much
easier option for you would be to use Unicode (nchar, nvarchar and ntext)
instead of ANSI (char, varchar and text) for your string fields on
sql-server.

Also, when you want to post to more than a single newsgroup, it's better to
make a crosspost than a multipost; see:
http://www.cs.tut.fi/~jkorpela/usenet/xpost.html .

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"RG" <nobody@xxxxxxxxxxx> wrote in message
news:508AA6DC-9221-425F-B175-76E4E84AB22F@xxxxxxxxxxxxxxxx
I have a access db version 2000 running on ms access 2003. There are bunch
of
tables linked to sql server 2005 db. Based on what I have read so far,
odbc doesn't do codepage translation. Hence, I better make sure that ms
access has the same code page as that of sql db. How can I find out what
character codepage ms access is using?

Thanks in advance


.