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:
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: