Was the issue resolved? How? I am seeing the same error in an Access DB, yet I have other Access DB's running my exact same code, and they are not getting the error?