About avoiding the mixing of queries created under different ANSI SQL query modes (MDB)

A query that uses wildcard characters in a criteria expression can produce different results under each query mode. For example, if you run:

• An ANSI-89 SQL query in a database set to ANSI-92 query mode, such as:

  SELECT * FROM Customers WHERE Country Like 'U*'

  It returns all customers from a country/region named "U*", not all countries/regions beginning with the letter "U", because the asterisk (*) is not a wildcard character in ANSI-92 SQL.

• An ANSI-92 SQL query in a database set to ANSI-89 query mode, such as:

  SELECT * FROM Customers WHERE Country Like 'U%'

  It returns all customers from a country/region named "U%", not all countries/regions beginning with the letter "U", because the percent sign (%) is not a wildcard character in ANSI-89 SQL.

If a query uses an alias that is the same as a base column name and you create a calculated field using the ambiguous name, the query will produce different results under each query mode. For example, if you run the following query:

SELECT Orders.OrderID AS Freight, Orders.Freight, [Freight]*1.1 AS [New Freight] FROM Orders;

Under ANSI-92 SQL, Access calculates the New Freight value using the Freight field, and therefore increases each Freight by 10%. Under ANSI-89 SQL, Access calculates the New Freight value using the Freight alias, and therefore increases each OrderID by 10%.

In general, avoid doing the following to prevent problems caused by mixing queries created under different ANSI SQL query modes:

• Converting an Access database set to ANSI-92 SQL query mode from 2002 - 2003 file format to 2000 or 97 file format. ANSI-92 SQL query mode is only supported in the 2002 - 2003 file format.
• Changing the ANSI SQL query mode for the current database after you've created one or more queries. If you must do this, retest the existing queries to ensure that they still run or produce expected results, and rewrite the queries if necessary.
• Importing queries created under one ANSI SQL query mode into an Access database set to another mode, or exporting queries created under one ANSI SQL query mode to an Access database set to another mode.
• Changing the ANSI SQL query mode in an existing application. This could break your application and require rewriting your application.

  In Access 2000, you can only programmatically change the ANSI SQL query mode and any queries created under ANSI-92 mode were hidden in the Database window. In Access 2002 or later, you or a user can change ANSI SQL query mode through the user interface and ANSI-92 queries are no longer hidden in the Database window, so you should help prevent accidental or intentional changes to the ANSI SQL query mode of your application by helping protect your code and helping prevent the changing of the query mode through the application's user interface.

• Using ambiguous aliases and column names. To avoid confusion, ensure that aliases and column names are always unique in an SQL statement.