Rants are more than welcome. We make games here so this .Net/database stuff
is new and frightening to me :) I wouldn't be touching it at all but it
seemed like the best tech to use for a particular tool we're writing
(project/task management stuff; it's like watching paint dry, only less fun)

Anyway, the table in question does have a primary key defined, an int field
that serves as an autoincrementing ID. Identity spec, seed and increment are
set on the DB side. If I use the designer to create a dataset and hook it up
to a simple grid view that seems to work ok, which leads me to believe the DB
is set up right.

Unfortunately my needs are a little more complex than slapping it into a
grid at design time. I need to generate at least the Select at runtime based
on the user to pull a custom list, and for usability purposes the data
displayed in this view is split between a few different controls. This much
at least is working fine and was actually easy to set up. The next step was
updating the source when changes are made on the client, which is where it
falls down (thus answering Marina's question).

I've tried setting the MissingSchemaAction::AddWithKey as well as explicitly
calling FillSchema() but I still can't get the bloody thing to give me any
commands. I've also copied the Update statement from the generated dataset
and explicitly added it as the Update command in the programagically created
one, but it doesn't actually update. That I don't know what to make of but
since assuming the fetal position and crying isn't an option I'm going with
the theory that I missed a key step somewhere.

--
Scott Bruno
Shiny Entertainment