[RESOLVED] Write textbox value to field in table with VBA coding

[lilmark]

Well, I guess it's just my vb 6.0 coding that's got me thinking the way I first said.

What is fldfoo? is that supposed to be the unique identifier so it knows which record to point to?

How would I right the sql statement if I wanted to updated multiple fields/textboxes the same way?

And, here's more info, just in case it clears some of it up. I have a subform pointing to the same table. On the subform I have a textbox linked to the primary key just so I can see which record it's currently on. As soon as the user types info into the subform the textbox linked to the primary key populates with 68 for example letting me know it's on the new record 68.

Now, if those earlier text boxes on the main form are not bound when they hit the command button wouldn't it put the values of those unbound text boxes into the record 68 since it's currently pointing there as they entered the new data in the subform?

[Al42]

How would I right the sql statement if I wanted to updated multiple fields/textboxes the same way?

Either multiple SQL commands or make the Where clause include all the records you want to update. Which way you do it depends on your data and the update criteria.

... Where fldIndex = 68 ...

would update one record.

... Where fldFoo = 'Administrator' ...

could update many records.

As far as many fields:

strSQL = "UPDATE tblInfo SET fldName = '" & Me.TextBox1.Text & "', fld2Name = '" & Me.TextBox2.Text & "' ... WHERE fldFoo = somevalue"

And, here's more info, just in case it clears some of it up. I have a subform pointing to the same table. On the subform I have a textbox linked to the primary key just so I can see which record it's currently on. As soon as the user types info into the subform the textbox linked to the primary key populates with 68 for example letting me know it's on the new record 68.

Now, if those earlier text boxes on the main form are not bound when they hit the command button wouldn't it put the values of those unbound text boxes into the record 68 since it's currently pointing there as they entered the new data in the subform?

No, the SQL statement isn't looking at the subform to figure out which records to update, it's looking at the Where clause.