When working on a database opened from LOCAL storage, network events like undocking and re-docking a laptop may trigger this error because an ODBC-connected resource was ALSO open (like a linked table in datasheet view). other open objects, like an open querydef which is NOT open in a network-attached connection to an ODBC resource now CANNOT be saved because Access will throw the above error message endlessly - and in this case, senselessly.

The above error should only be thrown when Access cannot successfully re-attach to or reopen a failed network connection or resource. (I am obviously not counting circumstances where pending transactions or delayed data-write operations were left hanging and disrupted by the broken connection, here; Those should be rolled back per normal database process rules.) However, writing something back to a LOCAL storage location should never get disrupted by this error message. It now does (at least in Access 2010!).