I just did another test and when it is on the network drive it does not appear to delete the lock file in time and that is why it cannot overwrite the original database when the compact is done, thus creates another. When on the local drive the lock file deletes very quickly and thus it can overwright the original when the compact is complete.

Does anyone have a suggestion on how to set it where it waites a specified delay before...

In a test that I ran when compact on close was enabled everytime I closed the database that was on a mapped network drive it created the extra database numbered as you described. I verified I had all the correct permisions in the folder that the database resides.

I then copied the database to my local drive and the problem of creating the duplicate database whent away. I repoend the one on the network drive and again the problem...