Question : Windows Server 2003 not releasing file lock on Access database

I have users in one office that are attempting to run a "compact & repair" in Access and they are not able to because they receive messages from the server that says "file in use by (user X)".  USER X is not logged in, and workstation USER X utilizes is, in fact, OFF.  I would think this is a problem with USER X except that it happens FREQUENTLY with DIFFERENT users and DIFFERENT workstations.

Their regular IT person says that it is a problem with our *application* but we have it installed in over 100++ offices and no one else has this issue... It is simply an Access db residing on the server, with a C++ front end on the w/s.  

BTW, USER X WAS NOT THE LAST ONE TO EXIT THE PROGRAM.

Answer : Windows Server 2003 not releasing file lock on Access database

We run a access database on our Windows 2003 Enterprise server.  I have to perform regular compact and repairs on the database.  Depending on how many users your organization has.  I work for a small business, so it's a lot easier.  I have everyone shut down their computers.  This lets me know, there's no one on the database, when you go to do the compact and repair.  If the lock file is still there, then I restart the server.  When I log onto the server the lock file is usually gone.  I have had one instance where the lock file was still there.  So I use this freeware program called unlocker.

http://ccollomb.free.fr/unlocker/
You can delete the lock file, with this program.  

I backup the database before the compact and repair, I also save it on another remote location.  If you're able to use a copied version of the file for test purposes can you compact and repair that database?  If so I don't think it's an application issue.  I think it's just because someone is on the database, when you go to do the compact and repair.  

I should mention that we use access 2000, we're a small business.  I don't know if deleting that lock file with a 2003 database would cause any problems.   So please delete your lock files at your own risk.