Well that was the question, what's the best way to do this (sample code would help or a pointer in a direction).
Everything i've checked online requires an sql statement as below...
cmd = New SqlCommand("INSERT INTO Options([Field1],[Field2],[Field3]) Values (@Field1, @Field2, @Field3)")
cmd.Connection = db.conn
With cmd.Parameters
.AddWithValue("@Field1", Field1)
.AddWithValue("@Field2", Field2)
.AddWithValue("@Field3", Field3)
End With
The code above is what i was referring to in my original statement 'updates require an sql statement' ....
Also, Thanks for the link, looking at it now (and will take a bit to go through) but believe it is essentially the same as i've seen everywhere. One or the other, not all in a single place like my original code.
----------------------------------------------------------------------------------------------
Updated: Just checked out the page/code samples, according to the code it's called Inline sql.
After a 'quick' view, the code functions given are pretty much useless as they are hard coded to the number of fields passed, to me, you would need to code a function for each table and every possible combination (or pass an array)
If this is the most streamlined coding for what I need to do, pretty much explains all the issues with M$ products the exponential increase in size and resource required!
But do appreciate the quick reply and the pointer to the sample code!