Fix the issue with UniqueTables property when used with ADODB (to connect Access with SQL Server).
We have an existing Access database which uses ADO to connect to SQL Server (not using ODBC). It works when run with Access 2010 but fails with A2013 or A2016. I understand that this is a known issue with a hotfix for A2013 (but not A2016). We are moving to A2016 near the end of this year. Without a fix the property cannot be used and the result is that the form is Read-Only.
Jim Conrad commented