Data Bindings
-
Instead of updating in usual way, i use a simple binding for my data entry. It works but my problem is the last record that i recorded did not update. Only the previous records are updated, but the last did not. my code for 'update' button is:
Me.BindingContext(DataSet21).EndCurrentEdit() Me.OleDbDataAdapter2.Update(DataSet21) MsgBox("Grade recorded!") -
Instead of updating in usual way, i use a simple binding for my data entry. It works but my problem is the last record that i recorded did not update. Only the previous records are updated, but the last did not. my code for 'update' button is:
Me.BindingContext(DataSet21).EndCurrentEdit() Me.OleDbDataAdapter2.Update(DataSet21) MsgBox("Grade recorded!")Rharzkie wrote:
DataSet21
Rharzkie wrote:
OleDbDataAdapter2
Wow! Have you ever thought of actually giving your variables descriptive names? What does DataSet21 mean to anyone anyway?
Upcoming events: * Glasgow: Mock Objects, SQL Server CLR Integration, Reporting Services, db4o, Dependency Injection with Spring ... "I wouldn't say boo to a goose. I'm not a coward, I just realise that it would be largely pointless." My website
-
Rharzkie wrote:
DataSet21
Rharzkie wrote:
OleDbDataAdapter2
Wow! Have you ever thought of actually giving your variables descriptive names? What does DataSet21 mean to anyone anyway?
Upcoming events: * Glasgow: Mock Objects, SQL Server CLR Integration, Reporting Services, db4o, Dependency Injection with Spring ... "I wouldn't say boo to a goose. I'm not a coward, I just realise that it would be largely pointless." My website
It's the result of dropping data access components onto the form designer, which I would go as far as to call worst practice.
Stability. What an interesting concept. -- Chris Maunder
-
It's the result of dropping data access components onto the form designer, which I would go as far as to call worst practice.
Stability. What an interesting concept. -- Chris Maunder
-
Rharzkie wrote:
DataSet21
Rharzkie wrote:
OleDbDataAdapter2
Wow! Have you ever thought of actually giving your variables descriptive names? What does DataSet21 mean to anyone anyway?
Upcoming events: * Glasgow: Mock Objects, SQL Server CLR Integration, Reporting Services, db4o, Dependency Injection with Spring ... "I wouldn't say boo to a goose. I'm not a coward, I just realise that it would be largely pointless." My website
-
Just answer my question ok.. To run your program properly and to write the correct codes are more important that giving a descriptive name. I can run my program properly even though i did not change the name of my variables...
Rharzkie wrote:
To run your program properly and to write the correct codes are more important that giving a descriptive name
I beg to differ - If you wrote this mess in the company I work for no-one would be happy with you. If you wrote this, then disappeared off (or got yourself fired - which, if you are writing code in this way, would be quite likely) and someone else had to maintain it, they would definitely be very unhappy with you.
Upcoming events: * Glasgow: Mock Objects, SQL Server CLR Integration, Reporting Services, db4o, Dependency Injection with Spring ... "I wouldn't say boo to a goose. I'm not a coward, I just realise that it would be largely pointless." My website
-
Just answer my question ok.. To run your program properly and to write the correct codes are more important that giving a descriptive name. I can run my program properly even though i did not change the name of my variables...
But giving things descriptive names is part of good programming practice. It is never acceptable to leave something in place that cannot be easily identified at a later stage. The important thing to remember here is that it only takes you a couple of seconds to rename them before there is any code present, but as soon as you have code that refers to it, you have to take much more care and this takes time.
Please visit http://www.readytogiveup.com/ and do something special today. Deja View - the feeling that you've seen this post before.