Losing Database Changes

[warthog72]

Ok, this is an absolute mystery to me. My database reverted back to an older version of itself, long after specific changes were made. Lets say this:

1. I made changes to the database Mon, Tue, and Wed.
2. Thursday I checked that everything was working fine and even made a change to 1 report. Actually, I made a change, saved the report, printed the report, made another change, repeat :||
3. Friday, I'm playing with the database and I get an error, do you want to notify MS - no, why bother.
4. TODAY, no more database. I'm now looking at my database from more than a week ago. None of my changes from all last week are even there.

Has anyone ever witnessed this? This isn't a SAVE / CRASH kinda problem. This is something inside Access. Perhaps a problem with thier MSSYS tables??

Any help would be greatly appreciated!

Thanks,

Steve
snewman_2000@yahoo.com

 

[willir]

Steve

More info about your workstation and network environment may be helpful.

Some things to consider...
- If this is a shared database, somebody requested a restore from IT becasue it stopped working

- IT had a system problem or a user requested a restore for another problem. IT restored from tape, and either accidentally over wrote your database, or had not other options on the restore. (For example, the file requested resided in the same directory as your database, and instead of restoring the file, IT restored the directory)

- Another user specifically copied an older copy of the database on top of the newer copy.

- (I have done this myself so please dont take this personally) Prior to working on the database, you made a backup copy. But now, instead of updating the copy, you accidentally older copied of the backup over top of the original.

All four scenarios involve an older copy of the database being copied over the newer copy. Access, by itself, can not decide to roll back x-days of changes, espcially if playing with forms and or design.

This issue provides an example to...
- backup the database
- keep a good copy of the database
- prevent human error, and use a script to perform the backup if manually backing up the datbabase
- if important, make sure you have sufficient security

Richard

 

[warthog72]

I considered all of those already, but since I'm the ONLY IT person in the office, the only admin for our SBS2k, the only person who handles any backups and restores, I eliminated all of that.

The thing that brought to mind the sys tables was the last time something like this happend (ie, the system crash error reporting such-and-such to MS), I remember losing some code I had just previously written into a Module.

Oh, I've had my fair share of forget to save, etc, but this is a week's worth of work. Also, the file was in my documents on my XP box - which noone in the office knows how to get to.

I figured the sys tables went corrupt or perhaps I did something they didn't like and access went to fix the error and erased anything related??? I'm grasping now, but I did take your notes and moved the files to the network where they will get backed up everynight

 

[willir]

warthog72

For a person who has to wear so many hats, I wish you good luck. And I am sorry that you lost so much work.

Richard