Home / Chatral xxx com / Insufficient key column information for updating

Insufficient key column information for updating

You are currently viewing the Pro VB Databases section of the Wrox Programmer to Programmer discussions. I am joining two tables and displaying that data on a form that uses ADO. Description: Insufficient key column information for updating or refreshing. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. By joining today you can post your own programming questions, respond to other developers questions, and eliminate the ads that are displayed to guests. The process was working fine until I added another table. 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.

Properties("Unique Table") = "tablename" In that case, updating or deleting a row will only apply to "tablename" However, I think this property is only available with ADO 2.1 (i 'm not sure). Exactly the same situation, but I'm using a SQLServer6.5 stored procedure returning the Primary Key/Identity col and one other which gets updated. Insufficient key column information for updating or refreshing Hi, hope somebody can help. Adodc error: Insufficient Key Column Information for Updating or Refreshing 4. Insufficient key column information for updating or refreshing 6. Adodc error: Insufficient Key Column Information for Updating or Refreshing 8. HELP: 80004005 Insufficient key column information for updating or refreshing 10.This is problem number 9,569 I've had trying to convert to VB2005. This is problem number 9,569 I've had trying to convert to VB2005. When I try to delete a record from the recordset, I get the error: "Insufficient key column information for updating or refreshing." Does anybody know what this means? I placed some debug code and the current record is set correctly. 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. When the primary key information is updated, the following error message displays: "Key column information is insufficent or incorrect. I am the only one accessing the database, and the form.This error message only appears when the primary field is updated. Hi This error normally means Access can't work out how to identify and pass back to SQL-Server which columns to update because it doesn't have enough information."Enforce relationship for replication", "Enforce relationship for INSERTS and UPDATEs", and "Cascade Update Related Fields" are selected for the relationship.The Access Project form is a query of the primary table data only. I am selecting all of the key columns plus one non-key column from one table. You could also use the "Unique table" property, like: ado RS. It kinda makes sense what it is doing, you selected data from three tables into a recordset, when you delete a row from the recordset, it tries to delete from all the base tables. I suspected that as the problem, so just as a test, I changed the querey to be a very simple one. John Poe Since the user would delete records very rarely in my program, I created a delete procedure that opens a separate recordset containing just one table, then I moved to the record that I want to delete and deleted it.

178 comments

Leave a Reply

Your email address will not be published. Required fields are marked *

*