Interesting issue with compaction. Any ideas to eliminate?

I have stumbled upon an interesting issue with regard to compaction of
an access frontend database which resides on a DFS target that utilizes
FRS to mirror the sharepoint, and I was wondering if anyone knows a way
to overcome it.

For those who are unaware of DFS or FRS, DFS stands for Distributed
File System, and basically involves "mounting" various sharepoints that
reside on various computers underneath one special sharepoint. When
you access the mounted directory under the DFS share, you are invisibly
redirected to where the share really is. FRS stands for File
Replication System (I think. it could be Service, tho). If you
indicate that a particular mount point in the DFS share has two or more
target sharepoints, you can tell Windows to use FRS to ensure changes
to the files in the sharepoint are replicated to the other targets.
Both of these are built-in technologies of Windows 2003 server.

On to what I have observed. We have a frontend/backend Access 2003
database application residing on one of these FRS replicated
sharepoints, and have the option to compact the database on close
turned on. What I am seeing is that when the compaction occurs, the
frontend database is renamed to DB1.mdb, and this name change is then
replicated to the other servers. The name is never changed back again,
leaving the shortcuts that the users use to access the database broken.
I have turned off the compact on close option, and the effect stops,
so the issue is linked to compacting on a FRS replicated sharepoint. I
would like to turn the compaction back on, as the database tends to
grow rather large, but I do not want the database's filename to change.
Any ideas?

.

Relevant Pages

  • Re: Interesting issue with compaction. Any ideas to eliminate?
    ... > For those who are unaware of DFS or FRS, ... > that reside on various computers underneath one special sharepoint. ... > database application residing on one of these FRS replicated ... What I am seeing is that when the compaction occurs, ...
    (comp.databases.ms-access)
  • Re: Interesting issue with compaction. Any ideas to eliminate?
    ... >an access frontend database which resides on a DFS target that utilizes ... >For those who are unaware of DFS or FRS, ... >reside on various computers underneath one special sharepoint. ... What I am seeing is that when the compaction occurs, ...
    (comp.databases.ms-access)
  • RE: Undeletable Form
    ... An even less welcome discovery was that compaction did not remove ... Eventually I finished up with a database which was nearly ... > It's an object already marked for deletion by Jet. ... > delete class objects from the Project Explorer window. ...
    (microsoft.public.access.forms)
  • Re: Backup Linked BE Tables
    ... be shown to be closed via code, the program execution stack and memory used ... database at the same time. ... and then you should be able to run that compaction code you have. ... I'll have to assume that you have some connection code that opens up the ...
    (microsoft.public.access.modulesdaovba)
  • Re: Windows mail can compact the message store.
    ... Windows Mail doesn't need message compaction, ... store (database) compaction. ...
    (microsoft.public.windows.vista.mail)