Synchronisation problem

[papyturbo]

Delicate problem. let me try to explain clearly the scenario :
- I have 2 PCs,
++ Bouzin = mobile, which I use all the time
++ BigBouzing = fixed, essentially a full backup of the other (in case of problem, have not worked on it for more than 2 weeks)
- during my work, I prepare a delivery (software) for a
client. Synchronise all before going out - OK
- at my client's, I modify some files.
- return to my office, do some more work, synchronise again. One essential file (Access file "LeanTCF.mdw" = security settings) is modified, copied to BigBouzing - OK. Both files on both machines are now dated 6
June 2008 (same time)
NOW, while still working on Bouzin, I realise a problem and revert to an OLDER copy of that same file, dated 5 june 2008. I copy that file on Bouzin and continue to work.
Synch runs twice a day.
The next day, I realise that same file has reverted to its previous version (???), and I have to copy it again from my (luckily not emptied) USB key.
This occurs 2 days in a row, untill I realise the synch keeps copying BACK that file (dated 6/6/2008) from BigBouzing to Bouzin.

This is where you could help (maybe ?) :
- I thought synchronisation kept a database in order to signal any conflicts, NOT JUST to compare timestamps (no need for a database to do that)
- I expected this synch/database job to, at least, show a conflict and refuse to copy anything either way. The only thing in the log is an ERROR, trying to copy from Bigbouzing to Bouzin while that file is in use.
- at best, I would expect it to replace the most recently MODIFIED file to the other machine (Bouzin -> Bigbouzing), rather that the file with the more recent timestamp (but NOT modified since last run).

My settings are :
- Copy files even if timestamp changes after initial comparison : YES
- Copy directly to destination : no
- Try to copy files in use : YES
- Use Volume shadow copy : YES
- Copy permission... : no
- Verify copy...:no
- No empty source... : no
- Replace newer target files... : disabled and off
- Synchronize/backup/repl... no
- no script
- no Archiving, no encryption/compression, default performance
- comparison : Size and timestamps
- all size and timestamps options OFF
- Time offset : 0
- CRCoptions disabled (and off)

I cannot use a backup: need to synch both ways, in case I (occasionaly) work on Bigbouzing.

I can send a copy of the log + database, if required.

Thanks

Etienne

[TGRMN Software]

Hello

Thank you for the report.

This is a known issue which will be fixed shortly. When restoring an older file, ViceVersa should mark it as a conflict, as you suggested. Right now, ViceVersa copies the newer file over the older file.

The new ViceVersa build will be posted in the next few days.

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

[papyturbo]

OK. Thanx for the reply.

Will wait and check.