Why cant I repair and compact my database? 2

[joshuafoo1980]

An error message is given: "You attempted to open a database that is already opened exclusively by user 'myAdmin' on machine 'SNGDH25LH31S'. Try again when the database is available."

BUT User 'myAdmin' is myself and on verification, 'SNGDH25LH31S' is the machine that I was using.

I will appreciate any help...

Regards
Joshua Foo

 

[lupins46]

What version of Access?

 

[hymn]

Here are some ways of dealing with corruption
Thread705-840870.

Hope this helps
Hymn

 

[joshuafoo1980]

Access 97... lupins, any help will be appreciated.

Thank you hymn, I checking out the related threads, hope I find something...

Regards
Joshua Foo

 

[lupins46]

Check in the task list that there isn't a msaccess.exe process running when you have exited Access.

I may be wrong here, but this doesn't look like an Access message to me. It looks more like a user programmed message. At what point do you get this message?

 

[joshuafoo1980]

Dear lupins,

What does it mean if a msaccess.exe is running after I exited Access? I am sorry that I cannot verified this yet because the problematic database is being used at a site, not in my office. The database I use in my office for development has no such problem.

User programmed message, I get what you mean esp since it does not come with an error code... It appears after I try to Repair or Compact the database...

As a matter of fact, even if I am not in Access, I cannot rename, move or delete the particular mdb. But if I make a copy of it, everything can be done but I will need to use a different name for it of coz.

Is there anyway I can post screenshots of the problem for better visualization?


Regards
Joshua Foo

 

[lupins46]

This begins to sound like a problem with file permissions.

However it could be an incompleted Access session so when you get the chance (and Access is not being used), display the task list (In Win2000 do Ctrl+Alt+Del and select Task Manager). See if there is any process running called msaccess.exe. If so click on it and then click End Process.

If there is no msaccess.exe then you could also check for the presence in the database folder of a file called xxx.ldb where xxx is the name of your .mdb file.
Delete this if you find one. But this would not cause the file problems outside of Access so I doubt if this is the issue.

Then it's back to checking permissions on the mdb file and the folder it is in. For an access application you normally need all permissions for the file and folder.

 

[AmberO]

I have had this problem several times. I think it is something to do with Windows - for some reason although the user has closed the database, Windows thinks the user account is holding the file. Rebooting the pc usually fixes the problem, else check the file permissions, as already suggested.

 

[joshuafoo1980]

Dear lupins and AmberO,

I will check for an incomplete Access session when I get the chance, thank you. Oh, regarding the xxx.ldb, normally one appears and disappears with using and closing the resppective xxx.mdb file, but for this problematic database, the xxx.ldb file remains there even after I exit the database. The most irritating thing is that I cannot delete or move this .ldb file...

For both the file and folder, the Type of Access should be Full Control right?

Thank you both very much for helping,

Regards
Chuan Teck

 

[jinglin]

I think your database might have been corrupted. Creating a new database and try to import everything from the old one.Hope it works!

 

[FeS2]

I had this happen also yesterday. I just closed Access and went back into it and then it let me compact and repair it. It has happened to me before also when other people are editing a record at that time.

 

[joshuafoo1980]

Dear jingling and FeS2,

Hmm, importing everything will be my last option, thanx thanx, I am just afraid that I forget to update certain links after importing... Might have lots and lots to update, hehe! Will keep this on my option list anyway, thanx.

Actually, the problem is I am sure no one else is logged on except myself... I tried closing and entering a couple of times too... The thing is I must log on to repair and compact right? So why does the warning say I am exclusively using the database which is obvious? Really weird error to me... Thanx anyway...

Regards
Joshua Foo

 

[maxhugen]

I've experienced a problem where the *.ldb file could not be deleted. Don't know why.

I created a copy of the *mdb (with new name), and tested that this new copy opened, closed, and compacted OK (which it did).

Then I deleted the original mdb. I could now delete the ldb file.

Last, I renamed the copy back to the original. problem solved.

HTH

Max Hugen

http://www.AlphaFinancial.com.au

Sydney Australia

 

[joshuafoo1980]

Dear maxhugen,

I had created a copy, which can be compacted and so on. But the problem is that I cant delete the original... Really have no idea why...

Regards
Chuan Teck

 

[maxhugen]

Hi Chuan

Hmmm... the not-so-wonderful world of Windoze may be the culprit.

I don't really have any idea here, but can you even move the original db to another location? If you can, try rebooting and then deleting again after moving.

Other than that, I'm afraid I don't know what else to suggest!

HTH

Max Hugen

http://www.AlphaFinancial.com.au

Sydney Australia

 

[Ed2020]

I'm pretty sure it's Windows, not Access.

Will it let you open the database exclusively? If so can you compact and repair then?

Ed Metcalfe.

Please do not feed the trolls.....

 

[joshuafoo1980]

Yoz maxhugen and Ed2020,

I cant move the original db to another location... That's why I am at my wits' end, hehe!

I can open the database but it does not allow me to compact and repair...

Thanks for the trouble guys!

Regards
Joshua Foo Chuan Teck

 

[MoLaker]

I looked back through this thread and did not see a specific reference as to whether or not the database in question is located on a network server, but I'm assuming so. I have encountered occassions when a user crashed out of an Access application for whatever reason and it left the network (Novell, Microsoft, etc.) file locking intact. The network admin guys typically had to go in and blow away the lock.

 

[willir]

Joshua Foo Chuan Teck

Here is a long shot. In Novell, you can set a system attribute to delete-inhibit. I suspect the Compact / Repair involves deleting / recreating the database. (How else does it free up space be removing deleted records, reindexing, etc.) If so, then an attribute such as delete-inhibit will prevent the action from occurring. Using delete-inhibit seems like a reasonable security precaution - prevent database from accidental deletion, but could cause a lot of frustration if the system admin is not there to explain it to you.

There are other attributes - copy-inhibit, rename-inhibit and the real dandy is execute-only (don't go there). There are more to file attributes than just the old DOS attributes.

Consider what OS you are using and the OS of the server.

Copying to a local drive should remove the server OS issues.

Viewing properties with Windows Explorer or the native OS tools should help you view all the attributes.

If this long-shot happens to be correct, then toggle the attribute, and compact / repair your database. You wish to set the attribute back after the compact / repair task has been completed - so much the wiser.

Richard

 

[joshuafoo1980]

Hi MoLaker,

Yup yup, it is located on a network server with lots of users using the database daily... Of course when I was doing maintenance, only I was logged on.

Thanks MoLaker for the interesting info... Now that u mentioned about the network admin guys, I just remembered that they have not replied my mail dated donkey days ago! Is there any way to verify this locking coz I doubt the network admin guys will be as helpful as you guys...

Regards
Joshua Foo