Home/ Questions/Q 6349985
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T21:43:29+00:00

Just a little background: I am using Access 2010 to create forms and VBA

  • 0

Just a little background: I am using Access 2010 to create forms and VBA code in an Access 2003 format database. For some reason, Access 2007 format databases always corrupt on me when I make changes and save them with a particular group of objects, but that’s for another discussion.

When writing VBA code in this Access 2003 database, any time my code breaks (via breakpoint or an unhandled error) and I make a correction, Access tells me that it can’t save back to the database because another user has it open. However, I am the only user working on the database; this is a local copy of the database and it’s sitting on my desktop.

The LDB file can’t be deleted because Access is using it. When I first load the database, I see my machine name and “Admin” when opening the LDB in a text or hex editor. After a break, I see that plus a duplicate entry, but this time around “admin” has a lower-case “A.”

Closing the database and reopening it fixes the problem but makes it needlessly cumbersome to debug my code. Anyone else encounter this issue and/or have a fix for it?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It might be helpful to know what your code is doing when this happens. Certainly that’s not normal behavior. For instance, are you opening another database with New Access.Application? Are you using ADO or DAO to access records in the database with a connection string?

    There are no external connections to the database at all.

    It may not matter if there are external connections to the database if you are using a connection string to connect to the open database; not sure but that may be seen as an external connection… you may want to use CurrentDB for DAO, or CurrentProject.Connection as your ActiveConnection for any ADO queries.

    I am assuming that this problem persists through reboots; but for the sake of argument, try closing out Access and going to the task manager to make sure you have no other instances of MSAccess.exe running. You might even try closing all Office products and/or making sure that Access is the only Office product running. I have seen some weird conflicts between Microsoft Communicator and Outlook; so it’s not entirely out of the question for Access to have issues with another MS product.

    You may also want to check the size of the database to make sure it’s not exceeded 2GB. That causes the infamous “Invalid parameter” error; perhaps it might be causing this as well.

    With no other details about how your program works, we may only be able to offer generic advice like this.

    • 0