dirtdogcan
Technical User
OK, I've dug myself into a hole and cannot get out...
I've recently upgraded from CR8 to 8.5 and upgraded my Informix ODBC driver from 2.5 to 3.32.
Aside from the ODBC driver doing funny things, I'm getting some odd behaviour from CR in report refresh mode. Note that the problems I am experiencing were not present prior to upgrades.
Scenario:
Querying data from 3 joined tables in Informix database - to date (prior to upgrades) these reports worked flawlessly with the tables joined as they always have been. Errors arise on refresh:
1. On Run or Refresh: ODBC Error: [Informix][informix ODBC driver] General Error.Syntax Error
2. Removing one suspect table with a questionable join for this same report- query runs fine
3. Running this report against just the one suspect table with no other tables joined - query runs fine.
4. Running this report against the suspect table with only a single valid join between the tables - error appears again.
This error replicates itself regardless of the type or direction of join to the suspect table.
It would seem that the suspect table is behaving badly, but it seems fine - The suspect table has been checked and all appears fine and the same query between the three tables works fine in Access, for example.
Is it me or is either the new driver or the new CR8.5 being more rigorous in table joins?
Any ideas before I pull the rest of my hair out?
Fraser
I've recently upgraded from CR8 to 8.5 and upgraded my Informix ODBC driver from 2.5 to 3.32.
Aside from the ODBC driver doing funny things, I'm getting some odd behaviour from CR in report refresh mode. Note that the problems I am experiencing were not present prior to upgrades.
Scenario:
Querying data from 3 joined tables in Informix database - to date (prior to upgrades) these reports worked flawlessly with the tables joined as they always have been. Errors arise on refresh:
1. On Run or Refresh: ODBC Error: [Informix][informix ODBC driver] General Error.Syntax Error
2. Removing one suspect table with a questionable join for this same report- query runs fine
3. Running this report against just the one suspect table with no other tables joined - query runs fine.
4. Running this report against the suspect table with only a single valid join between the tables - error appears again.
This error replicates itself regardless of the type or direction of join to the suspect table.
It would seem that the suspect table is behaving badly, but it seems fine - The suspect table has been checked and all appears fine and the same query between the three tables works fine in Access, for example.
Is it me or is either the new driver or the new CR8.5 being more rigorous in table joins?
Any ideas before I pull the rest of my hair out?
Fraser