Insufficient key column information for updating

I am using a Sequel Server backend with a Access Project front end.

insufficient key column information for updating-69

Please join our friendly community by clicking the button below - it only takes a few seconds and is totally free.

You'll be able to ask any tech support questions, or chat with the community and help others.

Delete I'd be curious how you reached the particular ado Master. Does your ado Master have SQL such that you expect to be at a certain record, or has the user somehow indicated a particular record to be deleted? Delete with a Msgbox to display some field(s) I'd expect to find in that recordset - that way, I'm sure I'm actually positioned at the correct recordset. If I've populated the record as expected, then....? The error is as follows : "Insufficient key column information for updating or refreshing" I know the table definately has a primary key because I created one I know I have permissions on the view because I added them I know the principle works because I extracted the VB key code into a sample application Incidentally, I'm attempting to update the record from a data bound grid, but I do get the same error with the . Insufficient key column information for updating or refreshing.

Also, my SQL query is as follows but I ruled out that the problem is there since I tried deleting records from the same query in Access and it seems to work fine.

Applications using ADO, which used to work in V8.1, may fail in V8.2 or higher. Starting V8.2, this returns the database name, and ADO uses it to reference a database object.

One such error is "Run-time error '-2147467259 (80004005)': Insufficient key column information for updating or refreshing." ADO uses 4 part naming convention when referencing a database column. Since DB2 doesn't acknowledge such naming convention, any function call may fail whenever a database object is referenced.

ADO, then, returns the error, "Insufficient key column information ..." Prior to V8.2, SQLGet Connect Attr() with SQL_ATTR_CURRENT_CATALOG simply resulted in a CLI error, CLI0150E (Driver not capable). More support for: DB2 for Linux, UNIX and Windows Programming Interface - .

We're a friendly computing community, bustling with knowledgeable members to help solve your tech questions.

To do so, it calls SQLPrimary Keys() and SQLStatistics(), and passes the database object names as the arguments. PATCH2=8 This instructs DB2 to ignore the catalog argument even if it is passed in a function.

DB2, however, does not recognize the database object names because of the naming convention problem above, and returns no data. For more information on PATCH2, please refer to the Information Center.

The code is virtually the same as my VB6 project which works fine. Thecode is virtually the same as my VB6 project which works fine.

Tags: , ,