Insufficient base table information for updating or refreshing

For example, some applications have failed when the unique key was made up of 20 or more fields, apparently because there are more fields than their internal design can handle.

To resolve the problem, create a unique key on the table.

These applications require additional restrictions on the table design; typically, a restriction is that the table have a unique key.

Application Requirements: Note that the cause of these problems is clearly indicated by the error message returned; however, some applications can suppress the i Series® Access error message. Typically, this is seen when the file does not have a unique key and the application is attempting to use a keyset or static cursor.

Run-time error '-2147217865 (80040e37)' - Client Access Express ODBC Driver (32-bit)[DB2/400 SQL] SQL0204 - "q Custcdt" in "qiws" type *FILE not found.

Some versions of the MDAC parser appear to assume that all names are quoted identifiers (case-sensitive names).

Later versions of Microsoft® Access (, for example) lifted the requirement that a unique key actually exist and prompts the user to select field(s) making up a unique key.For example, the SQL statement "Select * from qiws.q Custcdt" generates the error message listed above.An SQL log shows that MDAC built the SQL Statement "Insert into "qiws"."q Custcdt" ....".The programmer can also prepare and run their own update, insert, and delete statements.This method is required for positioned updates (dynamic, server side cursor with update lock concurrency).

Leave a Reply