SQLSERVER2K supports these code pages:
Central European Windows - CP 1250
Central European DOS - Latin 2 (CP 852)
So CP 852 is not supported and advanced CP - COLLATIONS are used.
For example, for Czech language (Central European) use collations:
/* SQL collations */
/* Widows collations */
Suffixes _CS,_CI,_AS,_AI specify Case and Accent sensitivity.
You also can add suffixes _KS,_KI,_WS,_WI (Kana and Width sensitivity), but they are not used.
With suffix _BIN raw binary data are used, fast, but dangerous.
Then binary stored:
CP1250 (1 B) when char /varchar /text datatype is used
UNICODE (2 B) when nchar/nvarchar/ntext datatype is used
Collation affectes comparing (linking) and sorting data (grouping,indexes).
Use COLLATE translating option to change behavior of query.
select 'abcd' COLLATE Czech_CS_AS
0. ACP on srv win2k:1250, OEMCP: 852 (clients: the same)
1. I'm runnig Polish_CI_AS on sql 2k (it ansi)
2. I have application via ODBC (so it is ANSI app) -> Latin 2 (1250) (more, internally it converts ascii (oem 852) to ansi 1250 before sending into srv via odbc)
1+2-> no translation AutoAnsiToOem is needed (if apply nothing should heppens: ansi to ansi)
3. finally there is 3rd party soft (MS Access) also via odbc -> also ansi, connected to to the same db.
so ascii codes runs like follows:
main app: sends ascii (after internal converting into 1250 ascii) - no translation of ascii- srv stores ascii
connecting with access: I see ascii
the problem is I'm runnig all of them as ansii clients and server: so there is no translation; but main app used to translate from ansii 2 ascii herself.
so I thoght to install sql srv as oem in native mine cp 852 to force DB-Function: AutoAnsiToOem.
translating storage into unicode is not possible: more than 300 tbl's in dbd and app doesn't like it
thx in advance, pawel
Try adding replace of ascii by ascii in trigger or application before insert/update.
>> it is not possible, I have no influence what app sends. I put that trig in SQL srv and I will work with "backup" table with required dataset format,.
I wanted to find "native" solution for sql srv but probably I failed.
What about "Perform translation for character data" check box in ODBC?
>> do not work
I heard about translation tables for cp's in Fox Pro ans Sybase ODBC connectors but I cannot find them.
P.S. If your are completly rewritting your starting post, are you able to change its subject from ASCII 582 to ASCII 852?
>> pardon I was sleepy and tired