That usually indicates that your server table has no primary key and no
unique indexes. When you created the link you were prompted to designate
which fields could be used by Access to identify unique rows and you
supplied a field (or fields) that are NOT actually unique on the table.
For example if I link to a table with no primary key that contains two
fields (FirstName and LastName) and I tell Access to use those fields to
build a local unique index (required to allow updates on such tables), then
I update the row having "John" and "Smith" in those two fields, I will
actually be applying that update to ALL of the rows on the server where
FirstName has "John" and LastName has "Smith".
It is best to actually have a PK or unique index on all of your server
tables, but if you don't and you tell Access to use one or more fields to
build a unique index on then you MUST correctly specify fields that are
actually unique. Otherwise you run a serious risk of trashing your data.
thanks for the quick reply.
I tried to select columns when I linked the table, but that did not
work.
I select group, plan, start date, end date, first name , and last
name.
got the same error.
there really is not a unique record for this table, I'm bulk loading a
set of records that could contain some dups.
(which are ok the system that we are loading into will handle them ,
via it's own update)- Hide quoted text -
- Show quoted text -