Thank you for your post.
If you haven't run into any corruption with the back-up file, then continue to use it. Be sure to also keep frequent backups for the near term.
You may also want to run a Recover on the backup file to ensure no errors are reported. Although 99+% of the time, it's fine to use a Recovered file, consider rebuilding the file, creating each table and layout from scratch. Once finished, import all data from the backup file, remove the backup file, and place the newly rebuilt file into production.
Thanks for the info TSGal. I did some digging around and found an old back up from 2010 and it successfully past recovery. Would you stil recommend re-building from scratch? Unfortunately, this seems to be something that was overlooked for quite some time during by the previous developer and plenty of functionality was added to this DB... I'm rushing right now to rebuild in fear of the file crashing again so I may re-build the best back up, get that into production (after testing) and then start rebuilding from scratch.
It looks like the immediate concern is to get the solution running quickly. Therefore, do what you have to do to get the data to the clients.
As mentioned before, continue to keep frequent backups until you have a long term solution. You may or may not have to rebuild the file from scratch, but keep notes of any crashes that occurs from this time forward. Specifically, what was the client doing before the crash, what layout was being accessed, what table was being accessed, what script (if any) was being performed, etc. This may help narrow down any problem areas. Sometimes, a layout is damaged, and by creating a new layout and deleting the damaged layout may be all that it takes.