Search results

It was not the sql statement. It was trying to mix a snapshot query and a dynaset table into a dynaset query result.

Ok, the problem was trying to mix a dynaset table with a snapshot query. If I set the resulting query to snapshot, then we're able to sort results.

I have a query that is a table joined with another query of our company database. The query of our company database is actually a 'final query' joined together from 5 queries of the company database. There are a number of left() and trim() functions used in these queries. The query that is...

By the end user in the query output screen. They use the drop-down filters on the column header, and then the #NAMES?s show up.

The query built draws data from one of two places: a linked table in the _be and a query which draws data from our mainframe. Some testing suggests the failure only happens when the mainframe query data is involved. Here's a couple constructed queries: SELECT [qry_TR_All Truck Info].[Variant]...

We made a nifty page that can construct a query for users by selecting checkboxes and entering info into fields on a form. Then VBA code builds it into an sql statement, assigns it to the .sql property of our universal query, and opens the query. It works nicely until they try to sort on...