This can come from another instance of MS Access, a Microsoft Access add-in or library reference, a VBA Add-in, or other program such as VB6. If two instances of Microsoft Access (DAO database engine) are using different system MDW files, a conflict may occur where the database appears to be exclusively locked by the other instance. The MDW file used by your instance of Access can be checked in VBA by examining the value of DBEngine.SystemDB.Īnother copy of Access or DAO may have that database opened using another MDW file causing this conflict. This applies to MDB files (not ADP or ACCDB formats). It turns out that another cause of this error is not immediately obvious and is related to workgroup security files. What’s going on? Why would the second instance think it’s being opened exclusively? What if the Other User isn’t Opening it Exclusively? This error can occur even if the other user has the database opened without opening it exclusively. Maybe the other user opened the database in exclusive mode or made some modifications such as editing modules, which put the database in exclusive mode. This error occurs if another user (or instance of Access) has opened up the database exclusively and you try to open it. When you try to open a database, you may encounter this error message: Could not use file already in use.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |