Sounds like your query is optimizing each time you call QODBC, try:

SELECT DISTINCT CustomerRefFullName, EntityRefFullName, ItemServiceRefFullName FROM TimeTracking NOSYNC

instead to bypass the syncing operation.

Well, the reason why I have it off is because I want the new timer info that's entered in each day.  The query only runs once a day, so it really needs to get new data each day.  I understood the optimizer as a sort of cache and since I never need cached data, I thought I didn't need the optimizer.  My question to that is that most of the data is the same except for the last days data.  Would the optimizer be effective so that it sort of caches the old data and only gets new data, or would it get all the data when I select the "The start of every query" radio button?  I would have to choose this option because we don't run the query until everyone exports their time, which is usually a few minutes before we run the query.  Please advise.

-Jed

You need to have the optimizer on if you run queries like this:

SELECT DISTINCT CustomerRefFullName, EntityRefFullName, ItemServiceRefFullName FROM TimeTracking

because you are quering the whole TimeTracking table. If you are just wanting the new timer info that's entered in each day then you should be using a start from date:

SELECT DISTINCT CustomerRefFullName, EntityRefFullName, ItemServiceRefFullName FROM TimeTracking where TxnDate >= {d'2007-01-01'}

or better still, just today's date, whatever that is:

SELECT DISTINCT CustomerRefFullName, EntityRefFullName, ItemServiceRefFullName FROM TimeTracking where TxnDate >= {fn CURDATE()}

then there wouldn't be much need for the optimizer.