Base table information for updating or refreshing
Note that in each case the update ability is supplied by the Microsoft runtime or the application and not Client Access ODBC.
To resolve the problem, try upgrading MDAC, using a client side cursor, or changing the cursor and lock type.
Note that a unique key on the table might be required.
The problem has been seen with MDAC/ADO 2.5 and 2.6.In these situations, the application is actually deleting and updating records by running an UPDATE or DELETE SQL statement that has "WHERE too many indexes or too many fields in the unique key.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.The pound (#) sign is not a valid character in ODBC or in any ISO/ANSI SQL version.Although Client Access ODBC and IBM® DB2®/400 allow certain nonstandard characters, the DB2/400 SQL Reference strongly recommends using the invariant character set.