Error reporting synchronisation conflict

[papyturbo]

Hi,

- *.ldb files (Access locks) are filtered OUT of the synchronisation (no use)
- the synch reports a conflict because
--- one of them has been changed
--- the pairing one, on the other side, has been removed.
NO conflict should be reported in such cases, since the only way to remove that conflict is to copy it via VicerVersa (waste of time)
+ the fact that itis NOT visible in the full display window, because it is filtered! and has to be searched for manually...

Is there a chance that such conflicts will be ignored in a future release?

Thanx,

Etienne

[TGRMN Software]

Hello

was the "exclude" filter for this file added after the tracking database was created for the first time?

thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[papyturbo]

This goes a while back, so it is not impossible (sorry, u will have to do the test "to be sure, to be sure...") though I doubt it.
Normaly, I would have
- set up my backup (to network disks) first, with all include/exclude filters,
- then set up this synch between 2 PCs, for part of the sources only, and I would have copied the same filter settings from the backup settings.

Actually, what I realised yesterday was: the *.ldb conflict file did not appear in the full window, because I had closed Access in the meanwhile, and that file had been erased -> it was no longer available on either side of the synch!