oledb code page

[Peter Proost]

Hi group, I don't know if this is possible that's why I'm posting

I've got some old dbf-files (clipper) I have to update from vb.net, this
isn't a problem using oledb. But I've got one small problem, when I
insert some special characters like ß (the german Eszett) this doesn't
get inserted correctly in the table cause it has got codepage 437 and my
machine is running on the default 1252. So I asume the oledb provider
also uses the 1252 codepage, but is there a way to tell it to use 437?

Thanks in advance

Greetz,

Peter

 

[Cor Ligthert[MVP]]

Hi Peter,

Are you sure that it is 437 and the ß (the german Eszett).
http://www.microsoft.com/globaldev/reference/oem/437.mspx

the 1252 is however in my idea the same for that Eszett then the 437
http://www.microsoft.com/globaldev/reference/sbcs/1252.mspx

As it is a problem, why not wait until Vlaanderen is seperated? Just joking,
I think that Armin or Herfried can better help you, but a good place to wish
you "prettige kerstdagen". However I hope that the code pages give you some
help.

I have not the idea that OleDB has anything to do with used bytes, it is the
receiving place that has to be in the same code as the place it has been
set. (While that is in the German speaking Belgian in my idea not much
different from the French and Dutch part).

For those not understanding this message, it is based on the Benelux
culture.

Cor

 

[Peter Proost]

Hi Cor, also "prettige feestdagen voor u". Maybe vlaanderen can join the
Netherlands But we have a government now, because otherwise the
politicians couldn't go on christmas holiday... that says it all
I also wish I could be active again in the ng but it's so busy here at
work that I have to limit myself to posting an occasional question.

About the problem: Now I'm also not sure anymore what the cause is, but
I can tell you that both the server running the programm and the server
containing the dbf files are both english windows 2003 servers. I also
noticed that when I open the dbf file in visual foxpro 9.0 it asks to
specify a codepage so probably there wasn't one set when they were
created about 13 years ago. That's why I assumed that it would have been
the standard dos codepage 437 but it also could be 850. I'm going to do
some more research. In the meanwhile if anyone has any more tips they're
very welcome.

Greetz, Peter




Cor Ligthert[MVP] schreef:

 

[Peter Proost]

Hi just to tell that I've found a way that works for me to solve the
problem. When I for example update the dbf file with a command like this:

update profiel set description = cpconvert(1252,850,'text with special
character') where code = 'xxxx'

it converts the special char so that it's still readable in the dos app

cpconvert is a foxpro function to convert codepages

greetz,

Peter


Peter Proost schreef: