Access Eats Itself... SERIOUSLY!

[BusDriver3]

Last week I posted problem with a Access DB that once I completed it gave a "Run Time Error 3022"... So, I started over from scratch and created an entirely new Database... Which I backed up all along the way, I have several backups... I finished today. The entire Database is only about 300 megabytes.



Okay, I come back from a break and open my new Database and I got two dialogue boxes with these errors:

Record(s) cannot be read, no read permission on 'MSysObject'
and
Record(s) cannot be read, no read permission on 'MSysACEs'

Once I click okay on the dialogue boxes Access EATS ALL OF MY DATA... Everything is GONE! Seriously, how do I fix this!?

I copied and pasted one of the backup files and tried to open that and it got eaten as well!!!

I am starting to wonder if my profile on my network is corrupt. Any help with this would be GREAT!

[ItsMe]

Where did you paste the copy of the backup file to? Did you try pasting a copy to your local MyDocs folder?

[June7]

Want to provide db for analysis? Follow instructions at bottom of my post.

[ssanfu]

Have you tried opening the dB on a different computer?

[JamesDeckert]

Where is the DB stored on your HD?
It can't be in the Program Files folder.

[BusDriver3]

Answers to Questions:
-I was working with the file and saving it to my desktop (our network can be slow)...
-I tried to copy, paste and open it on our network ShareDrive and Access ate it there as well
-Unfortunaley I can't post a copy of the file, it can't be moved from off our network
-I even tried to import "Compact and Repair" and Access ate it

Thanks for the suggestions.
-I will try to copy and paste to MyDocs Folder.
-I will try from a different computer as well tomorrow.
-I will report back tomorrow.

[BusDriver3]

Here is what I did to get back on track.

I found one of my backups and made a copy of it and when I opened it, it didn't eat itself. Talking to some of my co-workers they suggested that I may have a hard drive that could be fragmented thus corrupting the file. They further recommended that I take that copy and save it to our network ShareDrive and work with the file there. That seemed to work... PFM I guess...