Modules Suddenly Missing?

[Bcanfield83]

Hi All,


I recently got an upgraded laptop with Windows 10 (64-bit) - previously was using Windows 7 (32-bit). Over the past couple days, my Access DB (.accdb file) keeps getting corrupt.. seems like whenever I modify something in the VBA Editor (in a Module or Class Module), the dreaded, "Database is in an inconsistent state" error will come up shortly thereafter. Thus far, it's able to repair the database each time - but prior to getting a new laptop, this never occurred.
Yesterday I ended up creating a brand new ".accdb" file and then importing all of the Forms/Queries/Reports/Modules from a backup version. The tables are all linked to a separate backend ".accdb" file (split database).
Currently I'm running into an issue where the modules are all listed in the Object Explorer, but then if I right-click on any of them and select "Design View", I receive the below error:
"The module name <xxxxx> is misspelled or refers to an object that doesn't exist".

If I go into the VBA Editor window, all of the Class Modules and Modules are missing.. They were there earlier this morning, but missing ever since I did another repair earlier today. Thoughts??

[ranman256]

This happen occasionally. Access 'crashes' and wipes out the entire VB code.
you must restore from a backup. (not the vb, restore the entire db)

[Bcanfield83]

I was able to restore them, though it seems that the "FE" database keeps getting corrupted ever since I received my new laptop.
Both the FE and BE .accdb files are on a network shared drive. There's a total of 3 people that use the database - but when opening it, I have a custom ".vbs" script (that I stole from somewhere) which creates a copy of the ".accdb" file under their UserID. So there's never more than 1 person in the main "FE" database at a time.
The other 2 people are also running this on Windows 10. The OS itself is the 64-bit version, but it's running the 32-bit version of MS Office. The FE and BE files were created by me using Windows 7 (32-bit version). Could there be compatibility issues there?
Yesterday I created a brand new ".accdb" file (on my new Windows 10 laptop) to use as the FE, then imported all of the objects over from the existing FE ".accdb" file. Then, linked all of the tables to the existing BE database. Yet it seems to keep getting corrupted (or on the verge of it - as per the "database is in an inconsistent state" error), like clockwork. This never happened until I started using the FE on my new Windows 10 laptop, so I'm thinking it must be some issue with that.. just can't figure out what it is specifically!