J
JoelB
Using the Unique Table and Resync commands, I was getting error when trying
to update a row I had just added. What I discovered was that instead of
using the table's primary key to resync with the database, Access was using a
column on which I had placed a unique clustered index. When I moved the
'unique' specification from the clustered index to a separate unique key
constraint, Access went back to using the primary key, and my problem went
away.
I post this in case some other poor soul is ever pulling their hair out over
this same issue!
[Access 2003, SQL Server 2005, identity column as PK]
Best Regards,
Joel
to update a row I had just added. What I discovered was that instead of
using the table's primary key to resync with the database, Access was using a
column on which I had placed a unique clustered index. When I moved the
'unique' specification from the clustered index to a separate unique key
constraint, Access went back to using the primary key, and my problem went
away.
I post this in case some other poor soul is ever pulling their hair out over
this same issue!
[Access 2003, SQL Server 2005, identity column as PK]
Best Regards,
Joel