Laccdb are not deleting from share drive (1 Viewer)

[Joy83]

Hi
I know a lot of threds talk about this issue but I tried all ways

i have full access I tried to remove it
I killed everything from task manager

what else I can do
Any suggestions

 

[isladogs]

Did you check in Background Processes in Task Manager?

 

[GPGeorge]

Hi
I know a lot of threds talk about this issue but I tried all ways

i have full access I tried to remove it
I killed everything from task manager

what else I can do
Any suggestions

"Which" share drive are we talking about? Who else has permissions to use the Access instance on it?

 

[Joy83]

Did you check in Background Processes in Task Manager?

Yes I did
Nothing there

 

[Joy83]

"Which" share drive are we talking about? Who else has permissions to use the Access instance on it?

Network drive
Server based

There are few who has full access
It’s locked by one of us we know who but we couldn’t fix it

 

[The_Doc_Man]

A "shared" drive could be either network-attached storage (NAS) or a drive on a Windows-based server.

Failure to delete the .LACCDB file for NAS could be related to permissions, but since the NAS usually doesn't have a formal O/S, it is hard to test whether someone actually still has the file open. All you can do for NAS is verify DELETE permission in the folder holding the file and, of course, DELETE permission for the file itself. (Obviously, if it is open, you already have READ permissions on folder and file.)

For the served-by-Windows case, however, it is possible to use the command prompt (CMD) to look at file locks via the OPENFILES command and determine the process ID of the process that is keeping it open. NOTE: To be able to disconnect the culprit connection, you must run CMD as Administrator. You can type OPENFILES /? to see what commands are available.

EDIT: You posted while I was researching... OK, for the Server-based case, you can look to see who has it open by connection name and can then disconnect it.

 

[GPGeorge]

Network drive
Server based

There are few who has full access
It’s locked by one of us we know who but we couldn’t fix it

Two "Last Resort" possibilities.
1) Bring in IT to handle it for you. Easier but stressful in some environments.
2) Bounce the server, i.e. restart it. Painful for a lot of people, but effective.

 

[The_Doc_Man]

If you cannot bounce the server, have you tried bouncing the machine of the person you think has it locked?

 

[Pat Hartman]

If no one has the file open, Access will close it if you open the app and then close it normally assuming you have delete permission on the folder.

Otherwise the last resort is to reboot the server.