I apparently was mistaken when I said the query did not contain any reserved words.
The query I was using was selecting from another query in the Access Database. That other query had a reserved keyword that was causing the problem.
BTW:
The Access database engine runs in different modes, depending on whether it is called from Access, data access objects, the Microsoft OLE Provider for the Access database engine, or the Microsoft Access ODBC driver. It can be run in either ANSI mode or non-ANSI (traditional) mode.
Because using these two modes results in two slightly different sets of reserved words, a query that uses a reserved word might work in one mode and fail in another mode
Keith