I have the same problem, this error pops up after the last few major MS updates.
The error occurs when a user double clicks on an Access 2013 front-end with an Access 2003 back-end but not when they double click on an Access 2003 database.
Having to fix the problem for every PC on the network is a real pain.
