Re: Troubles with informix ODBC drivers when using ms-access

Gerhrd Schmied <schmied@ima023.joanneum.ac.at> wrote: >I am developing a client/server application with an ACCESS-client and an >informix-server. At the beginning of my work everything went ok and I >didn't have any troubles at all. But now I am working with more >complicated queries which consist of about 80 columns. If I try to >insert new values into a table I get the error message "Query too >complex". If somebody could help me I would be pleased to get a short >message. Thanks a lot I think this one's been answered before, if not in this group then in other comp.database.* groups where Access and other databases' ODBC drivers are involved. If Access is not aware of any primary key for the table you are trying to update (e.g MyTable(Col1, Col2, Col3, ... Col80) as you say), then it identifies the row to match with SQL something like: UPDATE MyTable SET Col2 = "New Value" WHERE Col1 = "v1" and Col2 = "v2" and Col3 = "v3" and ... It can get worse than this, but you get the idea. The solution is to make sure the table has an index, and that the ODBC driver is providing that information correctly to Access. If you have ODBCTEST, try connecting to your datasource, then executing SQLIndexes and SQLPrimaryKey.