SQL Update question

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I'm venturing back into the unknown for me, I currently use DataCombo's in
my app, but it was suggested that I use regular ComboBox's instead. Of
course, this means that I will have to write the code to update my db with
the new information.

When I first wrote my app in Access VBA, I remember reading about a "dirty"
property, that if a control was changed/updated that control's dirty
property would be true. This way if you didn't like the change you could
dump the change and go back. You could also use the dirty property as part
of a test to see if you changed the value of a control or not. So my first
question, is there something similar in VB? I was not able to find a
"dirty" property, but there may be something similar...

Next, my app is all about viewing data in a db, there are approx 40 controls
on my form for displaying the data. When I'm in the edit mode and hit the
"update" button, would it be better to check and see if any thing has
changed and only update that, or would it be better to just parse through
all the controls and update the underlying db with whatever the current
value is?

I'm still conceptualizing here, and I'm open to any and all suggestions and
advice.

Thanks!

Darhl


.

Quantcast