Can't open DB! Super Emergency Pls Help Quick!

Originally Posted by tdw

This just happened this morning! When anyone, from any computer, tries to open our Orders Database, we get the following error message:

The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time. (Error 3197)


But that's not true! Nobody is on it!
Help! How can I get this to open? We rely heavily on this database, all day long!

Originally Posted by mmccarthy

First, check to see if there is an *.ldb file anywhere and see if you can delete it.

Originally Posted by tdw

I found one in C:\Program Files\Microsoft Office\Office11
called ACWZTOOL.ldb

Could that be it, should I delete it? The actual database file is on a server, should I search the server too before deleting this? By the way, I already tried copying the db file to my computer (which it let me do) then ran it. Same error. In case that means anything.

Originally Posted by mmccarthy

No you are actually only looking for one with the same name as the database. I take it this is only a single unit database and not a backend/frontend system.

Try copying and renaming the database and see will it open that way. Were there any upgrades to the office suite implemented recently?

Originally Posted by tdw

No upgrades that I am aware of. It was working fine last night.
But your question reminded me that when I tried to open it earlier the lower left of the window said "repairing" and had a progress bar, then my computer froze and I rebooted it. And yes, it is a single database file. I haven't educated myself yet on backend/frontend yet, so as far as I know that is not what we have.
I tried renaming the version that I just copied to my desktop, same error. However, a different copy of it that I have on my desktop (that I use for experimenting with) works fine.

Originally Posted by tdw

I wonder if rebooting the server would work?

Originally Posted by mmccarthy

I'm afraid to say it sounds as if the database has been corrupted by something.

I'll see if I can get some of the other experts in here for advice.

Mary

Originally Posted by tdw

The actual database file is on a server, should I search the server too before deleting this?

Originally Posted by tdw

Yikes! Okay, I am unable to find an .ldb...
The fact that it went into a repair automatically when I opened it this morning...is that evidence of corruption, or is the problem maybe that I had to reboot mid-repair?

Originally Posted by tdw

Yikes! Okay, I am unable to find an .ldb...
The fact that it went into a repair automatically when I opened it this morning...is that evidence of corruption, or is the problem maybe that I had to reboot mid-repair?

Originally Posted by mmccarthy

At a guess I would say this was caused because you had to reboot during a compact and repair.

Originally Posted by mmccarthy

Good suggestion Paul but I gather it's a stand alone database.

Originally Posted by mmccarthy

Just thinking. Check to see if Access dumped your database to a copy. It would probably be called db1.mdb and be in the same folder on the server.

Originally Posted by tdw

No, only the same files in that folder that there were before.
Should it have done a "compact and repair" without prompting for my permission first?

Originally Posted by prn

There are at least a couple of possible meanings for this: 1) "the program we run is on a server" or 2) "the program we run is on our desktop computers, but the data is on a server" or even 3) "the program we run is on a server and the data is also on a server, but possibly separate from the part we run".

Originally Posted by tdw

Sorry I keep posting after myself, but I'm kinda panicking and I want to respond to the above paragraph:
Not sure if this is what you meant, but each computer has the access software on it, the db file is stored on the server.

Originally Posted by tdw

And why would a backup copy (stored on the server) from last year not work, but a newer copy on my desktop works?

Originally Posted by prn

Oh Boy! If you rebooted mid-repair, that could be the problem all right. I hope that is not what happened. If you can get Access to repair the corruption you may be OK. If you can't, you may have to do something drastic like restore from last night's backups (you do back up every night, I hope) and possibly lose any work you managed to do between the backup and restore.

Don't do this lightly, though!

Losing your business data is a serious problem. If you need to restore your data from backups, then if you are not experienced in how to do that with minimal chance of losing anything, talk to someone who is. This is not a good time for "learning on the fly." And much as we all feel sympathy for you and your predicament, if is very difficult and really risky to try to talk someone through this from a distance. We can't see what you are seeing and we can't even be sure we know all the right questions to ask. Who set up your system? Can you get them to help you now?

(Holding my breath)
Paul

Originally Posted by mmccarthy

Try opening a new blank database and see if you can import the tables and other objects from the other database.

Mary

Originally Posted by mmccarthy

Compact and Repair can be set to run everytime the database closes. Open the good copy of your database. Go to Tools - Options. Under the General tab is the Compact On Close ticked? If it is I would untick it for now.

Originally Posted by tdw

I checked and no, Compact On Close is not checked.

Nobody admits to having had the file open overnight.

Originally Posted by prn

It could be worse than twice a week, but it could be better. Get your part-time guy to make it seven times a week! Even then, it's still possible to lose data, but the less you lose the better and it's generally hard to back up while your database is operational. (That's one of the features that distinguishes a big-time, big-business class database system from Access. :( )

See if you can get the last backup restored (without touching the current one) and see if you can test that on you PC.

Paul

Originally Posted by mmccarthy

If compact on close is not ticked on your computer it must be ticked on someone elses. If there are not too many users involved check each machine as this is an Access setting rather than a database one. Access shouldn't run a repair without prompting.

Originally Posted by mmccarthy

If compact on close is not ticked on your computer it must be ticked on someone elses. If there are not too many users involved check each machine as this is an Access setting rather than a database one. Access shouldn't run a repair without prompting.

Originally Posted by tdw

That's what I thought, but it did this morning. All I did was double-click the shortcut to launch the file, it opened Access, showed "repairing" with a progress bar in the lower left corner (application task bar?), froze, and I had to reboot.
No one has compact on close checked.

Originally Posted by tdw

Okay. We have had this happen once before, last year. But that time we thought it was because an older version of Access (2000) attempted to compact and repair. We use 2003 now and this time it DID NOT PROMPT for a compact and repair. It did it on it's own when I opened the file.
Is there ANY WAY to get it to repair that file again? I know where the compact and repair option is, but I would have to get the file open first, right? and it won't open at all.

Originally Posted by tdw

That's what I thought, but it did this morning. All I did was double-click the shortcut to launch the file, it opened Access, showed "repairing" with a progress bar in the lower left corner (application task bar?), froze, and I had to reboot.
No one has compact on close checked.

Originally Posted by mmccarthy

The only conclusion I can come to is that it was already corrupted and was trying to repair itself.

You said you moved from 2000 to 2003. Did you convert the database?

Originally Posted by tdw

Yes, it began a repair (a compact/repair I supposed, though all it said was "repairing") when I OPENED it this morning, and I was the first person today to try to open it.

We didn't MOVE from 2000 to 2003 exactly. The database was created by some other guy (who is now in jail, ironically) in, I believe, Access 2002, and did not set it up to be compatible with older versions. One of our computers last year was still running Access 2000, and we mistakenly clicked yes when it prompted us to do a compact and repair because it was corrupted. That in itself corrupted it worse because it tried to compact/repair a 2002 db using Access 2000. That time, however, it was not giving us the error message it is now. That time it was a corruption error message. All of the computers now have Access 2003, and from my understanding having a NEWER version should not hurt the 2002 file, is that right? No we never "converted the file", but I have been making improvements to it using 2003.

Originally Posted by prn

The one thing that keeps nagging at my mind is the question of how the various backup versions work or don't work. I find it extremely suspicious that an old backup does not work from the server, but a (different) old backup version does work from your PC.

I have to recommend taking (at least) those two versions and copying them to the opposite locations (i.e., the one from the server to your PC and the one that does work on your PC to the server) and trying them again from those locations. There looks to be something very fishy going on and I still think it would be worth checking. If the one that does work on your PC fails on the server, then we are definitely looking at an issue larger than just the one corrupted database (though that one is almost certainly corrupted by now even if it had not been before).

Originally Posted by prn

The one thing that keeps nagging at my mind is the question of how the various backup versions work or don't work. I find it extremely suspicious that an old backup does not work from the server, but a (different) old backup version does work from your PC.

I have to recommend taking (at least) those two versions and copying them to the opposite locations (i.e., the one from the server to your PC and the one that does work on your PC to the server) and trying them again from those locations. There looks to be something very fishy going on and I still think it would be worth checking. If the one that does work on your PC fails on the server, then we are definitely looking at an issue larger than just the one corrupted database (though that one is almost certainly corrupted by now even if it had not been before).

Originally Posted by tdw

I will try the swap. It seems very strange to me too that one copy works while another doesn't. Unless the corruption that occured was server specific, affecting all Access files on the server (conspiracy theory ;-) ).
Before trying anything very risky, there is one more option. I can have our IT guy come in and restore Monday's backup copy, then redo all of this weeks changes. It will be challenging to gather all of the info to do this, but it's not impossible. However, if old copies on the server are also not working, I fear that the same may be true after restoring Monday's backup of the db too. Fear unfounded? I hope so.

Originally Posted by mmccarthy

I don't think unfortunately we are going to get a quick fix on this issue. Let us know how you get on with the swap.

Originally Posted by tdw

I checked and no, Compact On Close is not checked.

Nobody admits to having had the file open overnight.

Originally Posted by tdw

Also, I have to go to the DMV, and considering it is Friday I'll be there forever. Thank you all so much for all you've done to help! I'll be back later.

Originally Posted by NeoPa

*Edit* This was the latest post when I prepared this - wow it's moving fast *Edit*

A way to determine if the file is (currently) open elsewhere, and therefore locked, is to try to rename it.
If it works then it isn't locked and you should probably rename it back straight away.
If it is, get your IT guy to determine where it's open and by whom.

Otherwise, I would listen carefully to Paul (prn) as he sounds like he knows what he's talking about. Remember, slowly and carefully is better than quickly and (OH F*CK!)

In answer to an earlier question, Access can often get its knickers in a twist without anyone doing anything wrong. It's almost certainly responded to something you did, but probably not anything you did wrong. Don't tell the boss, but rebooting (or crashing out) during the Repair process was certainly not a good idea - but it's a lesson learned, and you probably weren't to know.

Good luck.

Originally Posted by tdw

On renaming: it won't work no matter how I rename it, but it does let me rename it.

Originally Posted by NeoPa

The swap idea was a good one. The results surprised me as I expected the reverse.
As it is not a server environment (could have got complex) issue, I think the best approach at this time is one I think outlined by Paul and also taken up by tdw, which is to get the latest working version and try to bring it up-to-date manually.
Depending on what changes were applied (Data; Code; Form or report design), it may be possible to import them from the latest (corrupted) version.