Lingering Microsoft Access Record-Lock information file

[pb17]

Hi everyone,

I've been working with Enterprise Architect (EA) 15.1 and LemonTree 3.3.1 for a while now. Recently, I updated LemonTree to version 4.2.0 and noticed a strange behavior: in some cases—especially when conflicts are automatically resolved—the Microsoft Access lock file (which is usually created when writing to the model) lingers even after the merge process is completed.

This issue didn’t occur with the previous version. After a merge, the lock file would disappear as expected.

Has anyone else experienced this behavior?
Could this be causing issues with the EA database?

[Eve]

I'm not sure if the developers of LemonTree are active on this forum. I'd recommend directly sending them a support request.