MS Access won't "de-compile" a blank database (same error as with other non-blank databases)

Question

Microsoft Office Professional 2013   Version 15.0.5163.1000       

Microsoft Access  2013  (15.0.5115.1000)  32 bit

Windows 10 Home   Version 1903    OS Build 18362.295

Create a new blank database;   Attempt to Decompile the new database results in error message:

The database cannot be opened because the VBA project contained in it cannot be read.  The database can be opened only if the VBA project is first deleted.  Deleting the VBA project removes all code from modules, forms and reports.  You should back up your database before attempting to open the database and delete the VBA project.

Clicking Ok results in error message:   The Visual Basic for Applications project in the database is corrupt.

There is no code in the (blank) database for it to be "corrupt".

NOTE:   when I decompile an existing (different) database that has successfully decompiled in the past (and has not been modified recently) the decompile succeeds (at least it finishes without an error);  but if I copy that database to another folder and attempt to decompile it (without opening it manually) the above error occurs even though it is the exact same database as in the original folder.

The same error message is being received on an existing application when trying to decompile.  It is unclear at this point if there is actually corruption in the application.  There are other random issues with the application that were not occurring until recently.  Trying to track those down when I discovered that a blank database has "issues".  Not sure what to do at this point.

Also, when creating a new blank database and then attempting to copy over forms from an existing database (that experiences the decompile issue) the colors get "corrupted" along with the fonts;  not sure if this is related or not.  This would not solve my original problem since even the new blank database can't be de-compiled.

Question:  what do I do next?

Answer 1

OK, tried the Change/Repair option (on Office 2013) and that did not fix the issue.  (Did not Uninstall Access)

Not sure what to try at this point.

Answer 2

Gina

In reality a blank database does not give errors on decompile.   Have you tried that and did you get an error?  I was able to connect to my client's pc and created a blank database and decompiled without error.  I also decompiled the application (on his pc) without error.  So I am pretty well convinced that the issue lies on my pc with Access and not with the application.

I'm going to see if I can uninstall Access completely and re-install it.  Not something I've ever done before but I think it's my best option at this point.

Thanks

Answer 3

Okay, I get it now but blank database give errors on decompile because in essence nothing to do and there is no message for that.  However, something strange is going on because even with Objects you get the message with means there is something going on in there somewhere.  What References do you have set?  Also, have to unchecked *Track name AutoCorrect info* under Options?

Answer 4

Gina

While I appreciate your response I need to point out that I am not trying to decompile a blank database for no purpose.  My original post stated that "The same error message is being received on an existing application when trying to decompile.  It is unclear at this point if there is actually corruption in the application.  There are other random issues with the application that were not occurring until recently.  Trying to track those down when I discovered that a blank database has "issues".  Not sure what to do at this point."   So the question is:  is there something wrong with my original application  or not?  And will a successful decompile correct the issue?

The original problem is with an existing application that has recently been giving random issues that were not there previously.  In attempting to narrow the problem down I discovered that a blank database has the same (decompile) problem.  So I was hoping that someone would not suggest copying the objects from the existing application to a blank database.

I was trying to point out that I don't think the issue lies with the existing application but may be an issue with Access itself.  Not actually Access but maybe some DLL is out of synch.  For example, I see evidence (on web searches) that the current version of VBE7.DLL is 7.0.16.xxxx but I am assuming that means it is for Access 2016.  Can't find anything that tells me which is the correct version number for Access 2013.  But maybe there is another DLL that is out of synch.  (I recently updated to the latest update for Access 2013.)

Please also note that I stated that "Also, when creating a new blank database ..........  This would not solve my original problem since even the new blank database can't be de-compiled."

Thanks

Answer 5

So, not understanding why would you decompile a blank database, it serves no purpose.

If you are just looking to create a *clean* file then just open a blank database and import everything in.