Question : DFSr and Access Database issues & questions

We are running two servers with Windows 2003 R2 SP2 using DFSr. We are replicating a large number of folders between sites. I am well aware of how DFSr replicates and the sharing violations that can and will occur if you have users accessing files on both sides. What is troubles me relates to Access databases.
In one instance we have an Access database, most likely Access 97,  When a user accesses it, the ldb file is generated and then replicates across. This I have observed myself. What I have not observed is that the database updates while the user is in it, which is contrary to how DFSr works, but is what a user is telling me happens.
The other database is Access 2003 and when it is opened the ldb file is generated and it does NOT replicate across to the other server. If I create a file and rename it as an ldb it will replicate, but it does not when Access creates it so replication is working on this folder. The database does not update until the database is closed. All this I have observed
What I am trying to figure out is how Access databases and DFSr interact, or maybe just how these Databases work so I can relate that to how DFSr works. DFSr will not replicate changes until the file is closed and there are no locks. So why am I seeing different behavior?
Questions:
So are the two version of Access working differently with the mdb and ldb files?
1.      Does Access 2003 lock the ldb preventing replication and Access 97 doesnt?
2.      What would you think the expected behavior is for each type of DB?
3.      Can any of this be altered?
Basically I have a user who insisted that last week all databases replicated as soon as the user entered data and that all ldbs replicated, but I am not seeing that now and cannot verify how it was in the past. Looking for answers I can use to settle this issue. Thanks.

Answer : DFSr and Access Database issues & questions

The ldb file isn't generated until a user opens a bound form, query, report or table. It tells Access what records are locked and it's an important file.  However, it doesn't really matter if it gets replicated or not. It's just a snapshot in time of the current records that are locked. Access will deleted it and create another the next time a user opens another form.  They being made and deleted constantly.

1.      Does Access 2003 lock the ldb preventing replication and Access 97 doesn't?
         It does appear that way but I believe it's not relevant.  It's likely that any file that is open, is not replicated unless you might be able to define some replication rules.  How do your open commercial apps replicate?  If they do, then why?  Is it a setting or maybe a list of filetypes that the replication process is told to ignore?

2.      What would you think the expected behavior is for each type of DB?
        I would expect the ldb file to not be replicated as long as it's open, but with the VSS  service turned on, the server may allow it to replicate.  You might check with IT about whether that service is running.

3.      Can any of this be altered?
        No.  That's just the nature of a Jet database.

Check with IT about VSS on the server first.  Hope this was helpful.  Also, Share/folder rights might also prevent certain file functions from running.  You might check the rights on each of the folders to see if there any differences.

-a