Warning: The key defined by the KeyField property for table "alias" is not unique (Error 1495)

I get the following error:

Warning: The key defined by the KeyField property for table "alias" is
not unique (Error 1495)


The key specified for this table changed more than one row in the base table
for some of the remote view rows being updated.

Redefine the key using the KeyField view property


Can someone direct me to documentation that might explain what this error
means. The Microsoft documentation (above) is not helpful to me.
--
Thank You,

Louis

Dan
Mon Dec 05 16:02:06 CST 2005

You've specified a key field that isn't sufficient to uniquely identify rows
in the underlying table.

Specify a key field(s) that is sufficiently unique.

Dan

Thanks wrote:
> I get the following error:
>
> Warning: The key defined by the KeyField property for table
> "alias" is not unique (Error 1495)
>
>
> The key specified for this table changed more than one row in the
> base table for some of the remote view rows being updated.
>
> Redefine the key using the KeyField view property
>
>
> Can someone direct me to documentation that might explain what this
> error means. The Microsoft documentation (above) is not helpful to me.

Thanks
Mon Dec 05 17:53:35 CST 2005

Thanks for the help Dan.

No offense intended, since you are a real person, as compared to Microsoft,
but what makes a key field "key" and why do we care if it is key or non-key?

Dan
Mon Dec 05 18:10:34 CST 2005

A key field uniquely identifies a row in a table and is a fundamental
building block of relational databases.

Dan

Thanks wrote:
> Thanks for the help Dan.
>
> No offense intended, since you are a real person, as compared to
> Microsoft, but what makes a key field "key" and why do we care if it
> is key or non-key?

Cy
Sat Dec 17 17:21:42 CST 2005

Thanks wrote:
> Thanks for the help Dan.
>
> No offense intended, since you are a real person, as compared to Microsoft,
> but what makes a key field "key" and why do we care if it is key or non-key?
>
>
>
It sounds like your using an updatable view, and this requires that to
update a record you must define something in the table that is unique to
each record to make sure the correct record gets updated when you save
your chamges.