Open File Locks on File Server

I am currently troubleshooting an application that uses a
Microsoft 2000 database and is on a shared drive on a
Windows 2003 File Server. The database is used with an
application that connects to and opens the database and is
usually kept open all day long and used by multiple users.

Normally, when an Access database is opened, it creates a
lock file with the same filename and an '.ldb' extension.
When the last user disconnects from the database, the lock
file disappears.

The problem that is happening is that lock file is being
left open, even when no one is connected to the database
and not being deleted like it should be. Every once in a
while, the database gets corrupted and has to be repaired
using the ODBC admin tool.

I understand that if Microsoft Jet 4.0 (Access) is used
over a network that Microsoft recommends disabling
Opportunistic File Locking on Windows 2000 Servers, but I
see nothing about Windows 2003. Does anyone know anything
about this? Does the same procedures / recommendations
apply to Windows 2003 servers?

Note KB Article: 303528

Thanks all!