Ok: Sorry for the cross posting but I thought it was relevant. I have a Java desktop application that hooks to an Access 2003 database contained on a remote server. I make the connection to said db via the JDBC Bridge through an ODBC connection. Everything works great, it's reliable, moderately fast and cheap. However, lets say user A is the first in, so for some strange reason user A becomes Admin. All other users go about their work with no problem including Admin. I should say that the reason Admin is so named is due to the ldb file and the entry made in same. As you know, the work station ID is appended to the file and in the case of user A the word "Admin" is appended to the work station ID. So far so good. User A shuts down their connection to the db and leaves early for the day. Regardless if all users also shut down and then later on relaunch the application (connection) the ldb file still shows that user A is still Admin thus having a lock on the db. I have verified this over a period of time with many differing scenarios. No big deal, things keep churning and everybody is happy. Well, periodically I need to compact the db but I can't because it's locked and I'm informed of such. So, what's keeping the hook to the db alive? I've viewed my Task Mangler and there is no processes running on my end, all users have logged out and shut down their work stations. Any ideas? James M. Corbett A / Technical Specialist GST/HST Micros | Micros de la TPS/TVH Business Suite Assessing Systems (BSAS) Revenue and Accounting Systems Directorate (RASD) | Direction des Systèmes de revenu et de comptabilité (DSRC) Information Technology Branch (ITB) | Direction générale de l'informatique (DGI) Canada Revenue Agency | Agence du revenue du Canada (613) 941-1338 "...Is a hippopotamus a hippopotamus, or just a really cool Opotamus?"