UniqueTable property broken in Access 2013. Hot fix 2863871 will not work for Access (1 Viewer)

jwconrad

New member
Local time
Today, 11:00
Joined
Aug 15, 2016
Messages
3
We are using ADODB to "talk" to SQL Server from MS Access.

Everything works ok using Access 2010, but we are upgrading to Access 2016.

When I tried the database using 2016, I receive an error message that the "UniqueTable" property is not recognized.


I searched the web and found this is a KNOWN ISSUE and there is a hot fix (KB2863871) for Access 2013. But the hot fix will not run since I don't have Access 2013. And there doesn't appear to be a hot fix for 2016.


Other than rewriting the database to only update a single table at a time (no joined tables allowed), what can I do?


If I take out the UniqueTable setting, then the ADODB recordset becomes non updateable.

:banghead:
 

WayneRyan

AWF VIP
Local time
Today, 15:00
Joined
Nov 19, 2002
Messages
7,122
J,

You might try creating a View in SQL Server.

Link it as if it were a table and even assign it a PK if desired.

Hth,
Wayne
 

jwconrad

New member
Local time
Today, 11:00
Joined
Aug 15, 2016
Messages
3
Yes, I already tried that. The view is not updateable. :(
 

Minty

AWF VIP
Local time
Today, 15:00
Joined
Jul 26, 2013
Messages
10,354
You could create a stored procedure to do the update for you and call it from access using a pass through query...
 

jwconrad

New member
Local time
Today, 11:00
Joined
Aug 15, 2016
Messages
3
Thanks for the suggestion. I am looking for a quicker fix that doesn't require rewriting an already working solution.

In the meantime, I will investigate the amount of work required to implement your idea.
 

Users who are viewing this thread

Top Bottom