G
Guest
Access 2003. Several .mdb front ends are installed on workstations, linked to
a back end on a server. Several times I during fronnt end updates I have run
across front end .mdbs that will not go away when I try to delete them (eg,
to replace them with the new front end).
I get a message saying the file is either being accessed by anpther user or
maybe the disk is getting full-- neither of which is happening. Another thing
about these stubborn .mdb's is that when they are opened, a dialog box is
displayed saying the database is read-only and data and object definition
changes cannot be saved. (Actually, I like that idea, but that's another
issue...).
So-- what gives? How do I get rid of these mdb's?
THanks mucho!
a back end on a server. Several times I during fronnt end updates I have run
across front end .mdbs that will not go away when I try to delete them (eg,
to replace them with the new front end).
I get a message saying the file is either being accessed by anpther user or
maybe the disk is getting full-- neither of which is happening. Another thing
about these stubborn .mdb's is that when they are opened, a dialog box is
displayed saying the database is read-only and data and object definition
changes cannot be saved. (Actually, I like that idea, but that's another
issue...).
So-- what gives? How do I get rid of these mdb's?
THanks mucho!