ODBCLINK/SE Reference Manual (36217-90410)

ODBCLink/SE Reference Manual Appendix A Implementation Notes

ODBCLink/SE

©M.B. Foster Associates Limited 1995-2000 69

Note: Roman9 to PC-ANSI Translator will recognize and convert

the symbol used for the European Currency Symbol, the

EURO.

Some characters cannot be converted to ROMAN8 and then back to ANSI. For example, when the copyright sign in

ANSI is converted to ROMAN8, it is changed to a lowercase "c." When the data is returned to the PC client, the

cannot be properly converted from ANSI to ROMAN8 in a round-trip fashion. (The hex designation is listed along

with the character name.)

•_A6 broken bar

•_A9 copyright sign

•_AC not sign

•_AE registered trade mark

•_B2 superscript 2

•_B3 superscript 3

•_B8 cedilla

•_B9 superscript 1

•_D7 multiply sign

•_F7 divide sign

Similarly, the following characters, sent from the database server, cannot be properly converted from ROMAN8 to

ANSI in a round-trip fashion.

•_A9 accent grave

•_AA circumflex accent

•_AC tilde accent

•_BE Dutch guilder

•_EB uppercase S caron

•_EC lowercase s caron

•_EE uppercase Y umlaut

•_F6 long dash

•_FC solid box

Unsupported ALLBASE/SQL and IMAGE/SQL Statements

There are several reasons why some ALLBASE/SQL and IMAGE/SQL statements are not supported in the

ODBCLink/SE environment. They are explained here:

⊗ Several ALLBASE/SQL statements work only with embedded SQL;

ODBCLink/SE does not support embedded SQL.

⊗ Some ALLBASE/SQL statements relate to functions, such as connection,

that have been replaced by functions resident on the PC client.

⊗ Some ALLBASE/SQL and IMAGE/SQL functions are best restricted to the

DBA; statements which control these functions are accessible only through

Interactive Structured Query Language (ISQL) on the server.

⊗ ODBCLink/SE internally prepares an SQL statement to be dynamically

preprocessed. Therefore, you cannot use some statements such as

EXECUTE IMMEDIATE.