Access file corrupted?

[lilmark]

I've had this issue come up as of late.

I double click the access file to open it, but it does not open. However, next to the .mdb file a second file ending with .ldb appears which means I supposably running it, yet as I just said access doesn't appear. I try to deleted the .ldb file but of course it doesn't allow me to. Gives me an error saying something about sharing violation. So, now I can't access the file! However, if I leave it alone for a long time and come back later and try to delete the .ldb file it lets me and then allows me to open the .mdb file when I click on it again. However, if I close and open the .mdb file repeatedly it eventually takes me through that whole scenario again.

Has anyone heard of this before? If so, do you know what it means or how I can fix it? It's hard to work on a project if it decides not to let me in for awhile, ya know?

Side note, the .mdb is on a server which I remotely access through my laptop. Only thing I can think of is the request I send by clicking on it to open just gets hung up somewhere along the way to the server?

[Static]

it sound like the file is NOT closing...
re-create the error.. then open your task manager.. is ACCESS Running still?


ohh.. i just notice the "remote" portion of your post...
yuk.. working with access remotely is HORRIBLE.. im suprised u havent had more issues than this. yes, its getting delayed along the way.

[RobDog888]

If the mdb is on a Terminal server then that may also complicate the issue. If you create a new blank database and try the same scenerio does it also do the same thing or open normally?

[lilmark]

This has happened to me on two new databases I created and am working on. I'm new here btw. They haven't had this problem with previous projects that are already being used by other users. But, they are doing new stuff in the networking area and we've been having some issues with the server so I think that's the problem. Anyways, I found a fix for it. I just right click my computer, go to manage, select Shared Folders, Open files and right click and close the access files that aren't display for me. THEN, I log off my connection to the server and relog back into it and I can delete the .ldb file and open it. Of course, every time it hands up like that I got to do what I just said above again, but at least it works.

[RobDog888]

There was a know issue with Access on a Terminal Server where the Temp folder would be in a different place or something and causing disk or network error and not allow access to open the db, but your not getting any messages, right?

[lilmark]

Nope, I get no error messages. I just double click the access file to open it and it never appears, but the .ldb file appears next to it showing it's been opened/running. If I try to delete the .ldb file i get an error about a sharing violation. But, I just do the process I said in my last post and it lets me delete the .ldb and reopen the access file.