Home/ Questions/Q 8448789
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-10T10:31:28+00:00

I have an application that creates an Jet database at run-time, and imports ~100k

  • 0

I have an application that creates an Jet database at run-time, and imports ~100k records so that I can make use of the indexing for performance reasons (1 minute versus nearly 10 when not using a Jet database).

The database is created using ADO Extensibility in Excel, and everything works just fine. However, my issue comes whenever I then open the MDB file in Access front-end, it automatically starts to “repair” the database.

The data is still fine after the “repair”, however my main output query can not then be viewed in Access as it tells me it cannot represent the joins, and if I then view it in SQL the required joins are not there, and the query can no longer run. This still happens if I let it get “repaired” but do not open that query, i.e. it is the “repair” that breaks the query, not the act of trying to view it in Access. The funny thing about this is that I used the Access GUI query designer to construct the SQL as my life is too short to worry about it’s crazy bracketing style, but it then later decides that it’s too complex for itself??

Also, nothing else appears to be affected so I can only assume it’s this one query it doesn’t like.

This isn’t a deal-breaker for me as my fix is to make the MDB hidden and advise users who can see it not to open it.

However, I would really like it if the database could be opened and I didn’t have to hide it away like that. Therefore, my question is whether there is any way to prevent the MDB being “repaired” automatically?

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Microsoft Access is “repairing” the file when opened because it is missing some tables that are specific to the Microsoft Access user interface. Since you created the MDB file directly using OLEDB with Microsoft.ACE.OLEDB.12.0, these tables are not present, and must be created when Access opens the MDB the first time. There are several ways you can circumvent this:

    1) Name the MDB something other than .mdb – e.g.: MyAccessDatabase.mad – this will prevent Windows from using Microsoft Access to open the file.

    2) Use COM+ to open an instance of Microsoft Access, and have it create the .MDB file. This .MDB file will then have all the necessary tables present and will not need to repair the file.

    FYI, whenever Microsoft Access opens an MDB that needs repairing in this fashion, it will inspect all the QueryDef objects for invalid SQL and correct them as necessary. This is why your “complex” query is breaking.

    • 0