Language issues in client/server computing

Database users working at client applications may see or access strings from the following sources:

  • Data in the database   Strings and other text data are stored in the database. The database server processes these strings when responding to requests. For example, the database server may be asked to supply all the last names beginning with a letter ordered less than N in a table. This request requires string comparisons to be performed, and assumes a character set ordering.

  • Database server software messages   Applications can cause database errors to be generated. For example, an application may submit a query that references a column that does not exist. In this case, the database server returns a warning or error message. This message is held in a language resource library, which is a DLL or shared library used by SQL Anywhere.

  • Client application   The client application interface displays text, and internally the client application may process text.

  • Client software messages   The client library uses the same language library as the database server to provide messages to the client application.

  • Operating systems   The client and server operating systems may provide messages or process text.

For a satisfactory working environment, all these sources of text must work together. Loosely speaking, they must all be working in the user's language and/or character set.