Column control datagrid information insufficient key refreshing updating
I am binding this to a datatable in code using data Grid1. Default View and have a button that saves the changes using the Sql Data Adapter update method d Adapter.Update(d Table) The problem is that I want to disable editing the IC_DEF_CHAR_TEXT field when the record is Numeric and the IC_DEF_CHAR_TEXT when the record Is Text.However the changes made in the Text Boxes are no longer saved to the database during update.Can someone out there explain to me why the database is no longer being updated?
I was using an ADO data control in a VB 6 application. In otherwords, if you simply use bound text boxes for all of the fields in your ADO control (like I did), you will run into a problem if you try to change a field on the one side. Sub Description FROM Table1 INNER JOIN Table2 ON Table1. If your SQL statement results in a recordset with more than one record on the "many" side for each record on the "one" side, you might run into an additional problem if your form is not set up in a master/child relationship.
When I run the same SQL from Access itself, I am able to update some fields in the QUery, but not the ones that would update the "one" of the table. Maybe you can only use an ADODC based on a single table? So, for example, my SQL statement looked like this: SELECT Table1. What I discovered is that the problem was occurring because the foreign key in my "many" table had the same name as the primary key in my "one" table (a common practice).
Would very much appreciate suggestions and comments. So, for example, my SQL statement looked like this: SELECT Table1.
I checkd to see if my other post made it and it did according to my dejanews forum window.
By the way, you mention that you don't use bound controls much. Do you just find it easier to stuff the values into the controls yourself or is it better performance?
Search for column control datagrid information insufficient key refreshing updating:
I get the error "Insufficient Key Column Information for Updating or Refreshing". I am prepared to actually change the data under the covers by writing extra code to do that, but I need to be able to have the user change data on the form and then when they want to change records, I want to update the table data with their changes and then move to the next record. I next decided to isolate the problem down to the smallest number of fields possible. I could either leave out the reference to the foreign key in the SELECT section of my SQL statement, like so: SELECT Table1. After playing with cursor settings for awhile, I discovered it wasn't a cursor problem. Sub Description FROM Table1 INNER JOIN Table2 ON Table1. Item ID; I was able to eliminate the problem in two different ways.