Very Computer

i sometimes get this message from a vb 4.0 program attempting to open a .mdb
with shared read-only usage. the program is running under a user-id with
read (I have tried read-write permissions as well) permissions to all the
directories in the hierachy and including the directory where the .mdb file
resides (on a winnt server). there are no other users that have the .mdb
open, there are no .idb files in the .mdb directory.???????? what am i
missing?????
previous to this open attempt other programs/users with read-write
privileges have had the .mdb in question open for updates with exclusive and
read-write usage and i'm suspecting that somehow the locks from the previous
useage are not being cleared.
when this happens the only way i can clear the locks is to reboot the nt
server
anybody ever run into this and any solutions short of rebooting the
server???????
many thanks if you can help, i think i have thoroughly done the RTFM routine
with no help