Resync fails to use primary key

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
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

primary key - concatenated or autonumber? 6
Mail Merge Word Doc over SSL VPN 0
Primary Key (Identity) SQL vs Access 3
Changing existing primary key to autonumber 3
how can I generate non-clustered primary key? 4
unique composite key 6
Why won't Access assign a Primary Key ID to my linked SQL Table? 2
Update primary Key. 1

Top