Question Corrupt restored mdb file from back-up

[Tildha]

Hello,
I’ve been a member for a couple of months now, and have been reading posts on this forum for a couple years, but this is my first time posting. If there is anything I miss out on trying to explain my issue, please let me know and I’ll try to be clearer.
I use Access 2007 version (but still mdb files only), but what I will explain below happens when I used 2000 as well.
I work for a company where we have several MS Access databases. They are all mdb files, and our users who access the front end forms, they don’t have MS Access licence, but a Runtime 2002 component.
These mdb files are saved on Microsoft server, and they get backed up every evening using Altris recovery Solution 6.2 with SP3.
A few times, I’ve asked IT for a backed up version of the database, some of the restored files I cannot open but instead get the error message “Microsoft Access Not a valid bookmark.”
There is a Help button on the message, that refers me to Not a valid bookmark. Error 3159, but it doesn’t make sense to me as there is no VBA code written by the original developer or me in this project.
Is there anyone who’s had similar issues and might know how this can be solved/where I can find a solution for this? It’s not how to fix the file, but why I get the error message when opening up an mdb file that has been backed up.
Many thanks in advance, and as I said above, if there is anything I can add to make this clearer to understand, please let me know.

 

[boblarson]

It is totally possible that when the backup was taken, that someone was in it (had the frontend open, or worse - if it isn't split - the database open) and it won't necessarily copy correctly if it is open like that.

But what I would do is to decompile your current copy (and save a copy just in case it goes bad when doing the decompile) and then see how it goes for a while. But if this is not split, then it really must be - backend (tables only) on the file server and the frontend as a COPY on EACH USER'S COMPUTER.

 

[Tildha]

This was really useful. Unfortunately the database has been built with a front & back end in one file, but we do have long term plans to retire/replace it, which I’m now hoping to do sooner rather than later, as it’s very possible that the user don’t close it down at the end of the day (even if told otherwise).

Thank you also for the advice on decompiling the database, this is a process I’ve never heard of before and will start doing.

Many thanks,

 

[boblarson]

Thank you also for the advice on decompiling the database, this is a process I’ve never heard of before and will start doing.

Don't do that too often. Every once in a while is good and make sure to make a copy before you do, just in case something goes wrong.