Polish Translation

If anyone can help...
I have Win2K, I'm trying to transfer some Polish translations from an access
mdb into SQL Server 2000, the Polish translations never make it over. Is
there an update for Win2K or SQL Server available that I need?
--
mdHi michele
What do you mean by not make it? Is the data there but incorrect or not
there at all? Do you have any error messages? Is the collation correct on
your SQL Server instance?
John
"michele" wrote:
> If anyone can help...
> I have Win2K, I'm trying to transfer some Polish translations from an access
> mdb into SQL Server 2000, the Polish translations never make it over. Is
> there an update for Win2K or SQL Server available that I need?
> --
> md|||John Bell
What I meant by "not making it over" is this:
In my access db I have the Polish alphabet which has these special
characters: Å? Ä? Ä? Å» I have a vb script that takes my access data and puts
into the SQL Server. When the letters get to the SQL Server, I just have L A
E Z.
After further digging yesterday, I discovered that Polish is an ISO-8859-2
language and my SQL Server is configured for ISO-8859-1 languages. So now, I
guess, I need to configure SQL for the 8859-2. Any suggestions for that?
Michele
--
md
"John Bell" wrote:
> Hi michele
> What do you mean by not make it? Is the data there but incorrect or not
> there at all? Do you have any error messages? Is the collation correct on
> your SQL Server instance?
> John
> "michele" wrote:
> > If anyone can help...
> > I have Win2K, I'm trying to transfer some Polish translations from an access
> > mdb into SQL Server 2000, the Polish translations never make it over. Is
> > there an update for Win2K or SQL Server available that I need?
> > --
> > md|||Hi michele
My guess is that you need double byte characters rather than the single ones
you have therefore using nvarchar and nchar datatypes may cure this, although
if the transfer is (also) forcing single byte characters it may still be a
problem.
You may want to look at:
http://msdn2.microsoft.com/en-us/library/ms190245.aspx
http://msdn2.microsoft.com/en-us/library/bb330962.aspx
http://msdn2.microsoft.com/en-us/library/ms143508.aspx
John
"michele" wrote:
> John Bell
> What I meant by "not making it over" is this:
> In my access db I have the Polish alphabet which has these special
> characters: Å? Ä? Ä? Å» I have a vb script that takes my access data and puts
> into the SQL Server. When the letters get to the SQL Server, I just have L A
> E Z.
> After further digging yesterday, I discovered that Polish is an ISO-8859-2
> language and my SQL Server is configured for ISO-8859-1 languages. So now, I
> guess, I need to configure SQL for the 8859-2. Any suggestions for that?
> Michele
> --
> md
>
> "John Bell" wrote:
> > Hi michele
> >
> > What do you mean by not make it? Is the data there but incorrect or not
> > there at all? Do you have any error messages? Is the collation correct on
> > your SQL Server instance?
> >
> > John
> >
> > "michele" wrote:
> >
> > > If anyone can help...
> > > I have Win2K, I'm trying to transfer some Polish translations from an access
> > > mdb into SQL Server 2000, the Polish translations never make it over. Is
> > > there an update for Win2K or SQL Server available that I need?
> > > --
> > > md|||Wouldnt specific collation at the Column level help as opposed to configuring
the entire SQL for the 8859-2?
Thanks,
rgn
"michele" wrote:
> John Bell
> What I meant by "not making it over" is this:
> In my access db I have the Polish alphabet which has these special
> characters: Å? Ä? Ä? Å» I have a vb script that takes my access data and puts
> into the SQL Server. When the letters get to the SQL Server, I just have L A
> E Z.
> After further digging yesterday, I discovered that Polish is an ISO-8859-2
> language and my SQL Server is configured for ISO-8859-1 languages. So now, I
> guess, I need to configure SQL for the 8859-2. Any suggestions for that?
> Michele
> --
> md
>
> "John Bell" wrote:
> > Hi michele
> >
> > What do you mean by not make it? Is the data there but incorrect or not
> > there at all? Do you have any error messages? Is the collation correct on
> > your SQL Server instance?
> >
> > John
> >
> > "michele" wrote:
> >
> > > If anyone can help...
> > > I have Win2K, I'm trying to transfer some Polish translations from an access
> > > mdb into SQL Server 2000, the Polish translations never make it over. Is
> > > there an update for Win2K or SQL Server available that I need?
> > > --
> > > md|||Good thought - so I tried it - in the design view I changed my translation
column, collation setting to SQL_Polish_CPI1250_CI_AS. But when I run my
script to put the Polish translation into SQL, I lose the translation ( Å?
becomes L )
I'm working on my script now...
--
md
"rgn" wrote:
> Wouldnt specific collation at the Column level help as opposed to configuring
> the entire SQL for the 8859-2?
> Thanks,
> rgn
> "michele" wrote:
> > John Bell
> > What I meant by "not making it over" is this:
> > In my access db I have the Polish alphabet which has these special
> > characters: Å? Ä? Ä? Å» I have a vb script that takes my access data and puts
> > into the SQL Server. When the letters get to the SQL Server, I just have L A
> > E Z.
> > After further digging yesterday, I discovered that Polish is an ISO-8859-2
> > language and my SQL Server is configured for ISO-8859-1 languages. So now, I
> > guess, I need to configure SQL for the 8859-2. Any suggestions for that?
> > Michele
> > --
> > md
> >
> >
> > "John Bell" wrote:
> >
> > > Hi michele
> > >
> > > What do you mean by not make it? Is the data there but incorrect or not
> > > there at all? Do you have any error messages? Is the collation correct on
> > > your SQL Server instance?
> > >
> > > John
> > >
> > > "michele" wrote:
> > >
> > > > If anyone can help...
> > > > I have Win2K, I'm trying to transfer some Polish translations from an access
> > > > mdb into SQL Server 2000, the Polish translations never make it over. Is
> > > > there an update for Win2K or SQL Server available that I need?
> > > > --
> > > > md|||Hi michele
It could be the application which is not displaying the value correctly,
have you checked the ascii value?
John
"michele" wrote:
> Good thought - so I tried it - in the design view I changed my translation
> column, collation setting to SQL_Polish_CPI1250_CI_AS. But when I run my
> script to put the Polish translation into SQL, I lose the translation ( Å?
> becomes L )
> I'm working on my script now...
> --
> md
>
> "rgn" wrote:
> > Wouldnt specific collation at the Column level help as opposed to configuring
> > the entire SQL for the 8859-2?
> >
> > Thanks,
> > rgn
> >
> > "michele" wrote:
> >
> > > John Bell
> > > What I meant by "not making it over" is this:
> > > In my access db I have the Polish alphabet which has these special
> > > characters: Å? Ä? Ä? Å» I have a vb script that takes my access data and puts
> > > into the SQL Server. When the letters get to the SQL Server, I just have L A
> > > E Z.
> > > After further digging yesterday, I discovered that Polish is an ISO-8859-2
> > > language and my SQL Server is configured for ISO-8859-1 languages. So now, I
> > > guess, I need to configure SQL for the 8859-2. Any suggestions for that?
> > > Michele
> > > --
> > > md
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi michele
> > > >
> > > > What do you mean by not make it? Is the data there but incorrect or not
> > > > there at all? Do you have any error messages? Is the collation correct on
> > > > your SQL Server instance?
> > > >
> > > > John
> > > >
> > > > "michele" wrote:
> > > >
> > > > > If anyone can help...
> > > > > I have Win2K, I'm trying to transfer some Polish translations from an access
> > > > > mdb into SQL Server 2000, the Polish translations never make it over. Is
> > > > > there an update for Win2K or SQL Server available that I need?
> > > > > --
> > > > > md|||I got it working. I had to add the letter "N" before my data and it's
transferring correctly. Thanks for all the feedback, it has been helpful.
--
md
"John Bell" wrote:
> Hi michele
> It could be the application which is not displaying the value correctly,
> have you checked the ascii value?
> John
> "michele" wrote:
> > Good thought - so I tried it - in the design view I changed my translation
> > column, collation setting to SQL_Polish_CPI1250_CI_AS. But when I run my
> > script to put the Polish translation into SQL, I lose the translation ( Å?
> > becomes L )
> > I'm working on my script now...
> > --
> > md
> >
> >
> > "rgn" wrote:
> >
> > > Wouldnt specific collation at the Column level help as opposed to configuring
> > > the entire SQL for the 8859-2?
> > >
> > > Thanks,
> > > rgn
> > >
> > > "michele" wrote:
> > >
> > > > John Bell
> > > > What I meant by "not making it over" is this:
> > > > In my access db I have the Polish alphabet which has these special
> > > > characters: Å? Ä? Ä? Å» I have a vb script that takes my access data and puts
> > > > into the SQL Server. When the letters get to the SQL Server, I just have L A
> > > > E Z.
> > > > After further digging yesterday, I discovered that Polish is an ISO-8859-2
> > > > language and my SQL Server is configured for ISO-8859-1 languages. So now, I
> > > > guess, I need to configure SQL for the 8859-2. Any suggestions for that?
> > > > Michele
> > > > --
> > > > md
> > > >
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi michele
> > > > >
> > > > > What do you mean by not make it? Is the data there but incorrect or not
> > > > > there at all? Do you have any error messages? Is the collation correct on
> > > > > your SQL Server instance?
> > > > >
> > > > > John
> > > > >
> > > > > "michele" wrote:
> > > > >
> > > > > > If anyone can help...
> > > > > > I have Win2K, I'm trying to transfer some Polish translations from an access
> > > > > > mdb into SQL Server 2000, the Polish translations never make it over. Is
> > > > > > there an update for Win2K or SQL Server available that I need?
> > > > > > --
> > > > > > md|||Hi michele
The prefix character N denotes it is Unicode data when you have an constant.
See Books online topic "Using Unicode Data" for more.
John
"michele" wrote:
> I got it working. I had to add the letter "N" before my data and it's
> transferring correctly. Thanks for all the feedback, it has been helpful.
> --
> md
>
> "John Bell" wrote:
> > Hi michele
> >
> > It could be the application which is not displaying the value correctly,
> > have you checked the ascii value?
> >
> > John
> >
> > "michele" wrote:
> >
> > > Good thought - so I tried it - in the design view I changed my translation
> > > column, collation setting to SQL_Polish_CPI1250_CI_AS. But when I run my
> > > script to put the Polish translation into SQL, I lose the translation ( Å?
> > > becomes L )
> > > I'm working on my script now...
> > > --
> > > md
> > >
> > >
> > > "rgn" wrote:
> > >
> > > > Wouldnt specific collation at the Column level help as opposed to configuring
> > > > the entire SQL for the 8859-2?
> > > >
> > > > Thanks,
> > > > rgn
> > > >
> > > > "michele" wrote:
> > > >
> > > > > John Bell
> > > > > What I meant by "not making it over" is this:
> > > > > In my access db I have the Polish alphabet which has these special
> > > > > characters: Å? Ä? Ä? Å» I have a vb script that takes my access data and puts
> > > > > into the SQL Server. When the letters get to the SQL Server, I just have L A
> > > > > E Z.
> > > > > After further digging yesterday, I discovered that Polish is an ISO-8859-2
> > > > > language and my SQL Server is configured for ISO-8859-1 languages. So now, I
> > > > > guess, I need to configure SQL for the 8859-2. Any suggestions for that?
> > > > > Michele
> > > > > --
> > > > > md
> > > > >
> > > > >
> > > > > "John Bell" wrote:
> > > > >
> > > > > > Hi michele
> > > > > >
> > > > > > What do you mean by not make it? Is the data there but incorrect or not
> > > > > > there at all? Do you have any error messages? Is the collation correct on
> > > > > > your SQL Server instance?
> > > > > >
> > > > > > John
> > > > > >
> > > > > > "michele" wrote:
> > > > > >
> > > > > > > If anyone can help...
> > > > > > > I have Win2K, I'm trying to transfer some Polish translations from an access
> > > > > > > mdb into SQL Server 2000, the Polish translations never make it over. Is
> > > > > > > there an update for Win2K or SQL Server available that I need?
> > > > > > > --
> > > > > > > md|||Did you have to change the collation setting anywhere or adding N itself
addressed the issue?
"michele" wrote:
> I got it working. I had to add the letter "N" before my data and it's
> transferring correctly. Thanks for all the feedback, it has been helpful.
> --
> md
>
> "John Bell" wrote:
> > Hi michele
> >
> > It could be the application which is not displaying the value correctly,
> > have you checked the ascii value?
> >
> > John
> >
> > "michele" wrote:
> >
> > > Good thought - so I tried it - in the design view I changed my translation
> > > column, collation setting to SQL_Polish_CPI1250_CI_AS. But when I run my
> > > script to put the Polish translation into SQL, I lose the translation ( Å?
> > > becomes L )
> > > I'm working on my script now...
> > > --
> > > md
> > >
> > >
> > > "rgn" wrote:
> > >
> > > > Wouldnt specific collation at the Column level help as opposed to configuring
> > > > the entire SQL for the 8859-2?
> > > >
> > > > Thanks,
> > > > rgn
> > > >
> > > > "michele" wrote:
> > > >
> > > > > John Bell
> > > > > What I meant by "not making it over" is this:
> > > > > In my access db I have the Polish alphabet which has these special
> > > > > characters: Å? Ä? Ä? Å» I have a vb script that takes my access data and puts
> > > > > into the SQL Server. When the letters get to the SQL Server, I just have L A
> > > > > E Z.
> > > > > After further digging yesterday, I discovered that Polish is an ISO-8859-2
> > > > > language and my SQL Server is configured for ISO-8859-1 languages. So now, I
> > > > > guess, I need to configure SQL for the 8859-2. Any suggestions for that?
> > > > > Michele
> > > > > --
> > > > > md
> > > > >
> > > > >
> > > > > "John Bell" wrote:
> > > > >
> > > > > > Hi michele
> > > > > >
> > > > > > What do you mean by not make it? Is the data there but incorrect or not
> > > > > > there at all? Do you have any error messages? Is the collation correct on
> > > > > > your SQL Server instance?
> > > > > >
> > > > > > John
> > > > > >
> > > > > > "michele" wrote:
> > > > > >
> > > > > > > If anyone can help...
> > > > > > > I have Win2K, I'm trying to transfer some Polish translations from an access
> > > > > > > mdb into SQL Server 2000, the Polish translations never make it over. Is
> > > > > > > there an update for Win2K or SQL Server available that I need?
> > > > > > > --
> > > > > > > md|||I had done both: changed the collation setting and added the N. I just did a
quick test and set the collation setting back to <database default> and it
still worked. I will do further testing and report back if I find anything
different.
--
md
"rgn" wrote:
> Did you have to change the collation setting anywhere or adding N itself
> addressed the issue?
> "michele" wrote:
> > I got it working. I had to add the letter "N" before my data and it's
> > transferring correctly. Thanks for all the feedback, it has been helpful.
> > --
> > md
> >
> >
> > "John Bell" wrote:
> >
> > > Hi michele
> > >
> > > It could be the application which is not displaying the value correctly,
> > > have you checked the ascii value?
> > >
> > > John
> > >
> > > "michele" wrote:
> > >
> > > > Good thought - so I tried it - in the design view I changed my translation
> > > > column, collation setting to SQL_Polish_CPI1250_CI_AS. But when I run my
> > > > script to put the Polish translation into SQL, I lose the translation ( Å?
> > > > becomes L )
> > > > I'm working on my script now...
> > > > --
> > > > md
> > > >
> > > >
> > > > "rgn" wrote:
> > > >
> > > > > Wouldnt specific collation at the Column level help as opposed to configuring
> > > > > the entire SQL for the 8859-2?
> > > > >
> > > > > Thanks,
> > > > > rgn
> > > > >
> > > > > "michele" wrote:
> > > > >
> > > > > > John Bell
> > > > > > What I meant by "not making it over" is this:
> > > > > > In my access db I have the Polish alphabet which has these special
> > > > > > characters: Å? Ä? Ä? Å» I have a vb script that takes my access data and puts
> > > > > > into the SQL Server. When the letters get to the SQL Server, I just have L A
> > > > > > E Z.
> > > > > > After further digging yesterday, I discovered that Polish is an ISO-8859-2
> > > > > > language and my SQL Server is configured for ISO-8859-1 languages. So now, I
> > > > > > guess, I need to configure SQL for the 8859-2. Any suggestions for that?
> > > > > > Michele
> > > > > > --
> > > > > > md
> > > > > >
> > > > > >
> > > > > > "John Bell" wrote:
> > > > > >
> > > > > > > Hi michele
> > > > > > >
> > > > > > > What do you mean by not make it? Is the data there but incorrect or not
> > > > > > > there at all? Do you have any error messages? Is the collation correct on
> > > > > > > your SQL Server instance?
> > > > > > >
> > > > > > > John
> > > > > > >
> > > > > > > "michele" wrote:
> > > > > > >
> > > > > > > > If anyone can help...
> > > > > > > > I have Win2K, I'm trying to transfer some Polish translations from an access
> > > > > > > > mdb into SQL Server 2000, the Polish translations never make it over. Is
> > > > > > > > there an update for Win2K or SQL Server available that I need?
> > > > > > > > --
> > > > > > > > md|||Hi Michele
Unicode data is not depent on the collation.
John
"michele" wrote:
> I had done both: changed the collation setting and added the N. I just did a
> quick test and set the collation setting back to <database default> and it
> still worked. I will do further testing and report back if I find anything
> different.
> --
> md
>
> "rgn" wrote:
> > Did you have to change the collation setting anywhere or adding N itself
> > addressed the issue?
> >
> > "michele" wrote:
> >
> > > I got it working. I had to add the letter "N" before my data and it's
> > > transferring correctly. Thanks for all the feedback, it has been helpful.
> > > --
> > > md
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi michele
> > > >
> > > > It could be the application which is not displaying the value correctly,
> > > > have you checked the ascii value?
> > > >
> > > > John
> > > >
> > > > "michele" wrote:
> > > >
> > > > > Good thought - so I tried it - in the design view I changed my translation
> > > > > column, collation setting to SQL_Polish_CPI1250_CI_AS. But when I run my
> > > > > script to put the Polish translation into SQL, I lose the translation ( Å?
> > > > > becomes L )
> > > > > I'm working on my script now...
> > > > > --
> > > > > md
> > > > >
> > > > >
> > > > > "rgn" wrote:
> > > > >
> > > > > > Wouldnt specific collation at the Column level help as opposed to configuring
> > > > > > the entire SQL for the 8859-2?
> > > > > >
> > > > > > Thanks,
> > > > > > rgn
> > > > > >
> > > > > > "michele" wrote:
> > > > > >
> > > > > > > John Bell
> > > > > > > What I meant by "not making it over" is this:
> > > > > > > In my access db I have the Polish alphabet which has these special
> > > > > > > characters: Å? Ä? Ä? Å» I have a vb script that takes my access data and puts
> > > > > > > into the SQL Server. When the letters get to the SQL Server, I just have L A
> > > > > > > E Z.
> > > > > > > After further digging yesterday, I discovered that Polish is an ISO-8859-2
> > > > > > > language and my SQL Server is configured for ISO-8859-1 languages. So now, I
> > > > > > > guess, I need to configure SQL for the 8859-2. Any suggestions for that?
> > > > > > > Michele
> > > > > > > --
> > > > > > > md
> > > > > > >
> > > > > > >
> > > > > > > "John Bell" wrote:
> > > > > > >
> > > > > > > > Hi michele
> > > > > > > >
> > > > > > > > What do you mean by not make it? Is the data there but incorrect or not
> > > > > > > > there at all? Do you have any error messages? Is the collation correct on
> > > > > > > > your SQL Server instance?
> > > > > > > >
> > > > > > > > John
> > > > > > > >
> > > > > > > > "michele" wrote:
> > > > > > > >
> > > > > > > > > If anyone can help...
> > > > > > > > > I have Win2K, I'm trying to transfer some Polish translations from an access
> > > > > > > > > mdb into SQL Server 2000, the Polish translations never make it over. Is
> > > > > > > > > there an update for Win2K or SQL Server available that I need?
> > > > > > > > > --
> > > > > > > > > md|||As I remember, such a translation occuring on the client side (MS SQL OLEDB),
not server. In turn, OLEDB gets settings from the computer Regional Settings
in Control Panel.|||Hi
Unicode values are constant. From BOL:
The Unicode specification defines a single encoding scheme for most
characters widely used in businesses around the world. All computers
consistently translate the bit patterns in Unicode data into characters using
the single Unicode specification.
I believe if you are using non-Unicode data that is collation specific the
locales available may affect what is being displayed.
John
"Dmitrij Siemieniako" wrote:
> As I remember, such a translation occuring on the client side (MS SQL OLEDB),
> not server. In turn, OLEDB gets settings from the computer Regional Settings
> in Control Panel.