As Bill suggested, look at the command being sent back.
BTW, try doing a fillschema on your ds before doing a fill. That *might* fix
it, though that'd be in my eyes a very inefficent and bad solution - not to
mention the automatic command population is a real inefficient pig to start
with.
The best approach is to specify your own UpdateCommand so you have control
on what you're doing.
However since you are using Access, I am lead to believe that this is a one
user one d/b or close to it kind of situation, so you might even get away
with FillSchema only.
Anyway, give it a try and yes, you need to look at the command.
- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik
"Steve B." <(E-Mail Removed)> wrote in message
news:03FB19F5-65B7-45D8-B94E-(E-Mail Removed)...
>A particular column in my Access DB table, and the associated datagrid,
> cannot have duplicate string entries. I've selected "Yes (no duplicates)"
> for
> the Indexed Field Property of this column in the Access table.
>
> When I call update(), the DB gets updated but throws an exception saying,
> in
> affect, that I'm trying to change the key. This column is not the key.
>
> How do I handle this? How do I stop the ex.message being thrown?
>
> I guess I could always walk through the column searching for the value.
>
> Steve