|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||||
|
|||||||||||||||||
|
|||||||||||||||||
|
|||||||||||||||||
|
|||||||||||||||||
|
|
||||||||
|
|||||||||
|
|
|
|
Company
|
|
 SQL LINKS DEVELOPER SUPPORT
SEARCH Borland Online/Developer Support
Subject:Foreign characters (e.g. äÄöÖ ) in Interbase Foreign characters inserted into an Interbase table via Interbase Windows ISQL (WISQL) do not show up correctly in BDE applications. The reverse is also true, foreign characters entered into an Interbase table via the BDE do not show up correctly in WISQL. If a user attempts to change the language driver setting for the SQL Links driver or alias to something other than the default, an Interbase -802 error, "arithmetic exception, numeric overflow, or string truncation" occurs when the client application attempts to fetch a record containing these foreign characters. The error detail also says "Cannot transliterate character between character sets". Why? The default installation of the BDE sets the System language driver to "Paradox 'ascii'". This setting mainly controls how characters are stored and displayed. Since Paradox tables can only handle the OEM character set (i.e. the ASCII character set supported in DOS) that's how the BDE was "mapping" the characters. The solution is to change the the BDE's system language driver to something more appropriate, such as "'ascii' ANSI". PUB IB LINK CONFIG SW
|
|
||
|
|
|
|||
|
|||||
|
|
||||
 |
|||||
|
|||||
| Made in Borland® Copyright© 1994-2003 Borland Software Corporation. All rights reserved. Report Piracy, Legal Notices, Privacy Policy Last Modified Monday, 26-Mar-2001 16:27:09 PST |
|||||
