Database Needs to be Repaired

[RoseV]

This happens often. We have more than 5 users at a given time in Access db. I'll get the error that "another user may have unexpectedly quit application while in use..." and that the db needs to be repaired. I'll kick everybody out and then repair. Sometimes it runs thru without a hitch. Sometimes I have to contact our help desk because when I try to repair, I get the message that it is locked by another user on another machine...our help desk tells me this is on a server level that it is locked up. I need to know A) why it needs to be repaired and B) how can I prevent it from locking up on the server level. We did have this problem alot less often when there were less users; altho it did happen. Is this the problem? Any ideas??

 

[Junior1544]

I've seen this happen when I kick one of my users off their pc...

Meaning, They are logged in (all our pc's are win 2k), and lock the computer... Then they leave.. I need to get into it (we are in a shared office enviroment, we all use different computers with different login's), so I force log them off... then the db is corupt because it exited improperly...

Another thought that I've seen elsewhere on the threads here...

I've heard that if a pc has a bad network connection(not that they have no access, but it's just not a realy good connection), when the network get's disconnected for half a second, that can cause this to happen...

Both are things to look into...

(the last one, try to isolate down to one or two computers causing the problem, and replace their network patch cords...)

--James


junior1544@jmjpc.net
Life is change. To deny change is to deny life.

 

[psemianonymous]

There are a million possible causes. Check the corrupt MDBs FAQ (below) for several hundred of them.

Also, tens of Google threads:

http://groups.google.com/groups?hl=...dly+quit"&meta=group=comp.databases.ms-access

--
Find common answers using Google Groups:

http://groups.google.com/groups?group=comp.databases.ms-access

Corrupt MDBs FAQ

http://www.granite.ab.ca/access/corruptmdbs.htm

 

[Kotaro24]

This happens for several reasons.

The most common are those your help desk folks gave, i.e., somebody is not leaving MS-Access in a controlled manner. This includes flipping the power switch of your PC without exiting Access, and/or exiting a remote session (using Terminal Server or Citrix) without first closing Access.
End-user education can help here. Also, you probably want to find an ldb-viewer program to see what workstations were logged into the database when it went corrupt.

Another problem is code related. If your Access app has VBA code that is poorly written, it can cause frequent lockups. Also along these lines, if your database application isn't split into a front-end/back-end setup, it should be.

Finally, you could put the application on an operating system with better lock-handling capabilities. We had an Access application with 70 users that was crashing every day. We moved it from an NT server to a Novell Server and the application now goes corrupt 2 to 3 times per year.

 

[RoseV]

Thanks!

 

[pcgate]

RoseV:

I had similar problem and I fixed it by splitting the database into front-end and back-end. The front-end sat on the user workstations and the back-end; on the server.

EdgarJ

 

[RoseV]

Kotaro: It is split to a frontend/backend setup. Unfortunately, we are not able to relocate this to another server (I already asked about that!). Also, we have Ultra Edit 32 and it tells me everytime that ALL the users are in it. I actually believed it to be the manner in which they were exiting access (they never used it before I created this for them) and since I forced them to exit via the button on the main menu, we had the problem less. Now all of a sudden it's happening again. Any thoughts? I'm going to dig into those faq's Foolio pointed me to and see if I can't find some answers. If I can just figure out what the problem IS, I know I can fix it.
Thank you all for your help!

 

[jfgambit]

Rose:

There aer some things that you can do to prevent users from closing down the database improperly. Obviously, the only way to stop them from Turning off the machine is to hack off their hands, but I've found that they remove their shoes and use their toes.

I do have a sample db if you are interested that will disable the "X" closing of a database so that it can only be closed via the main Switchboard.

Let me know if you are interested. And give me an e-mail address.


"I know what you're t'inkin', ma petite. Dat Gambit... still de suave one, no?"

 

[RoseV]

Yes, I's like to check that out.
My guys liked to File/Exit while they were in the middle of running things - had to stop them from doing that! But don't know how to hide that "X" from them.
milker1975@hotmail.com
Thanks!