Not all of my "source" tables include primary keys (don't need it for my
purposes).  Unfortunately, that means I can't use the CommandBuilder to
generate SQL based on my SelectCommand.  I've tried to manually generate the
SQL commands (and they look right), but I seem to be missing a step because
then NO updating occurs (whether a primary key or unique field exists or
not).  I add the parameters (command.parameters.add), but that doesn't seem
to change anything.  The values I'm adding to the "source" are from an XML
file loaded into a dataset, so I'm not explicitly listing them in the code. 
These values will update to the "source" just fine when I use the
commandbuilder and the "source" table has a primary key or unique field.

Is there something else I should try or MUST every "source" table have a
primary key or unique field in order to write data back to the "source?"

This is a VB "classic" newsgroup. Questions about VB.NET (including VB 2005,
which has dropped .NET from its name) are off-topic here.

Please ask .NET questions in newsgroups with "dotnet" in their names. The
*.vb.* groups are for VB6 and earlier. If you don't see the *.dotnet.*
groups on your news server, connect directly to the Microsoft server:
msnews.microsoft.com.

Gee, thanks.  That's not at all clear from the website.  And I waited 3 days
for that answer.

Show quoteHide quote

Blame MS for re-using the name for a new language

My suggestion is to get a real newsreader; even outlook express is orders of
magnitude better than web interfaces for newsgroups.

VB.NET is the "New Coke" of the computing world.
Fuzzy Logic
Is VB6 still alive and well?
Weird...
Newbie help on String conversion needed please