Using the Query Designer with International Data

See Also      

You can use the Query Designer with data in any language and in any version of Windows®. The following guidelines outline the differences you will notice, and they provide information about managing data in international applications.

Note   For additional information about ANSI to OEM character conversion in SQL Server, see Query Designer Considerations for SQL Server Databases.

Localized Information in the Grid and SQL Panes

If you are using the Grid pane to create your query, you can enter information in the format that corresponds to the Windows Regional Settings for your computer. For example, if you are searching for a date, you can enter the date in the Criteria columns using whatever format you are accustomed to using, with these exceptions:

In contrast, data and keywords in the SQL pane must always be in ANSI (U.S.) format. For example, as the Query Designer builds a query, it inserts the ANSI form of all SQL keywords such as SELECT and FROM. If you add elements to the statement in the SQL pane, be sure to use the ANSI-standard form for the elements.

When you enter data using locale-specific format in the Grid pane, the Query Designer automatically translates it to ANSI format in the SQL pane. For example, if your Regional Settings are set to Standard German, you can enter a date in the Grid pane in a format such as "31.12.96." However, the date will appear in the SQL pane in ANSI datetime format as { ts '1996-12-31 00:00:00' } If you enter data directly in the SQL pane, you must enter it in ANSI format.

Sort Order

The sort order (collation sequence) of data in your query is determined solely by the database. Options that you set in the Windows Regional Settings dialog box do not affect sort order for queries.

Using Double-Byte Characters

You can enter DBCS characters for literals and for database object names such as table and view names or aliases. You can also use DBCS characters for parameter names and parameter marker characters. However, you cannot use DBCS characters in SQL language elements such as function names or SQL keywords.