RefreshLink Bug: "Primary key already exists"

Workarounds, status updates, and forum discussion links for the RefreshLink bug from the fine folks at AccessForever.org.

RefreshLink Bug: "Primary key already exists"

The Access MVPs over at AccessForever.org continue to do yeoman's work tracking and reporting on Access bugs.

Yesterday, Karl Donaubauer posted an article regarding the error message in the screenshot above.  Here's a description of the error from the article:

Description

When using the RefreshLink method for a linked SQL Server table in version 2312 build 17126.20190, you get error 3283 "Primary Key already exists". The affected build was rolled out to the Monthly Enterprise Channel (MEC) on February 13, 2024.

Check out the article on AccessForever.org for the current status of the bug and a list of workarounds until Microsoft rolls out a proper fix via the various update channels:

RefreshLink fails with “Primary Key already exists”
Description When using the RefreshLink method for a linked SQL Server table in version 2312 build 17126.20190, you get error 3283 “Primary Key already exists”. The affected build was rolled out to the Monthly Enterprise Channel (MEC) on February 13, 2024. There are several forum discussions about th…

While you're there, sign up for their mailing list to get alerts whenever they post about a new bug (or bug fix).

All original code samples by Mike Wolfe are licensed under CC BY 4.0