File in Use Error

[Guest]

I have a database which is split into Front End and Back End databases
(tables in the Front End are linked to tables in the Back End). The FE and
BE are both located on a Network share. I encourage Users to copy the Front
End to their own PC's as this is a more efficient . Users have change access
to the Network share.

The Front End on the Network can be opened up and works fine. However, if I
try to delete the Front End, I get a 'File in Use' error. I get this error
even when nobody has either the FE or BE databases open and there are no ldb
files present.

Can anyone please help to explain why the file is In Use when nobody is
actually using it and how I can overcome this situation to allow me to delete
the Front End (to replace by an newly updated one?

Could I remotely access the Front End and change a setting? A bit like when
you enable/disable the shift open action.

Thanks.

 

[Wayne Morgan]

Verify that the appropriate permissions exist in both the Share and NTFS
permissions. However, since no ldb file is present, if one does exist when
the database is in use, it definitely appears that deleting a file from the
location is not a problem.

On the server, right click My Computer and choose Manage. Go to System
Tools|Shared Folders|Open Files in the left pane. Does the database file
show as Open in the right pane? IF so, it should also show who has it open.
The "Accessed By" will be the NT network logon name. The Open Files window
doesn't automatically refresh (at least not very quickly). Pressing F5 will
refresh the window.

If the file shows as Open in this window, you won't be able to delete it.
You can right click the file in the window and choose to "Close Open File".
If you're sure the depicted user doesn't have the file open, this may solve
the initial problem. The question then becomes, why didn't the server remove
the locks on the file. For that, I would suggest the Windows Server
newsgroup for your model of Windows Server.

 

[Guest]

Thanks Wayne - good ideas to follow up. Trouble is, it is a corporate network
and, although I have full permissions to a share, I would have to involve
another team (the Server Admin team) to do the checks that you suggested -
i.e. to log on to the machine in question. That may be the only way to sort
this out ...