Corruption, ldb file not disappearing, etc.

[DataMiner]

I have been experiencing some very strange symptoms over the past week or so, and am looking for ideas. I have a number of different frontends that link to one or more shared backends. A week or so ago, all the frontends were reporting that one of the backends, PCAMaster_be, was corrupt (ie, "not a recognizable database format). I repaired it, it worked ok, and then a few hours later it was corrupted again. After going through this a few times, I rebuilt the be (imported everything into a new, blank db). Same thing -- it was OK for awhile, then became re-corrupted.

So, my conclusion was that:
a) one of my frontends was corrupting it,or
b) my shared library.mde file was the culprit, or
c) my shared .mdw file was the culprit.

I have been meaning to unsecure my db's for awhile becuase I don't really use the security in any meaningful way. So, spent most of the day yesterday going through the steps to unsecure. So, I'm not using anything but the default .mdw file now. I also rebuilt every single FE, BE, and the library.mde.

Now, PCAMaster hasn't gone corrupt again (yet), but I'm noticing several other bothersome symptoms:

1. In one of my FE's, when I close it, the application closes but it leaves Access running. I have to use task manager to get access to close.

2. Some of my .ldb files seem to stick around when they're not supposed to. I am 100% certain that NO ONE is using the db. But the .ldb file is still there and I can't make it go away.

3. I open a FE with the /excl command line option. It opens OK, but when I try to repair/compact, it won't let me. ANd if I try to make design changes, it says I don't have exclusive access.

ANy ideas appreciated on any of this stuff


Using Access 2002 and Windows XP

 

[CEH]

I'm sure you will get some better answers... but I'll pass along something that use to occur on a Access based software program we use at my work.... since they converted to sql server we don't get the problems.. BUT.... If users would not close out properly... from the frontend.. it tended to leave alot of hanging ldb files...... You might stress the importance of closing the application properly. I'm sure with all the hot coders we have on this forum someone has some coding to seek out and kill those orphaned ldb's

 

[KeithG]

Are you saying you actually try to delete ldb file and are unable too. I know there is a utility you can down load to actually view who is in the db. Do you get an error stating the file is in use whey you try and delete it.

 

[Jacob Mathai]

The front end users need read/write permission to the back end network. See if a user is linking with 'Read Only' permission. That could hang it up.

 

[MStef]

I have hed the same situation. Ask your network engineer to delete the "ldb" file. He can do it.