Access empty table why?

Question

Microsoft Access

My access database broke down, and there are many topics, yes I understand, but the problem is very atypical, so read the question and maybe someone will tell you some other version
of Karoche: the mdb base, weighing 380 mb (the size of the compressed database).
How they broke it: one well, very smart uncle tried to open it over the network, without one necessary library, it opened only with a good mother, closing it, he began to copy it, and another uncle at that time opened it from the local computer, breaking off and finding out why he began to wait. When copying ended and there and there the base ceased to open. Apparently the first smart uncle managed to do something with her when he tried to open it remotely. By open remotely here it is understood that this simple person simply launched the database through shared folders in a networked environment. In general, it is only necessary to leave and everyone will be able to break ... sad.
Now: the database opens, but an error pops up for all actions - Corruption was found in the MAccess file ... well, etc. with a suggestion to use the backup copy. There is a true exception: you can open tables in the designer, but you cannot open them in tabular form. Queries open in the constructor, and at the same time, you can create a query on the tables and it will display all the information. Several forms open in the constructor, but you can’t get to the VB code.
Failed: on all attempts to compress / restore, / DECOMPILE / Repair, export / import, it fails with the above error. JetComp, mdb_repair and their combinations work out the noman, but the result after them is the same, no, they really compressed the base a little, but the modules with the code still do not open. AccessRecover 2.2 generally said that everything is OK with the database, such as it is not necessary to compress it.
Task: the specificity of the database is such that you absolutely do not care about tabular data - new ones are constantly uploaded to replace the old ones. There is a backup copy of the database from a month ago, during this time only modules with code have changed, in which new functions with dynamism have appeared. requests, etc. I mean, the most important thing is to extract VB modules from this broken base!!!
I could not achieve this, the only thing is that by opening the mdb file in a text editor, I was able to find some of the pieces of code I needed, but I could not pull out all the contents of the module, everything is already very scattered and distorted there.
The question is: is there anything else that can be done to pull out the contents of the modules, or can we abandon this idea and start writing again the missing pieces of code?
PS I hope I didn't tire anyone, but at least you can laugh ... I still don't understand how these dudes managed to do so. break the base. Yes .. a bad deed is not a tricky one.