Restored Files get lost

[Way2Go]

In keeping with your Never Lose Data, Never, you always take the newest file and write over an older file without calling it a conflict.

This is wrong in ONE instance.

Suppose I destroy a Document and want to revert to an older copy.
I restore the copy from a backup.

Now I run Syncronization method which I find to always fill my needs because either the source or the target may change at any time.

The database files should have the original time stamps and ViceVersa should see that what happened is thus

Source Target Result
May 12th May 12th Synchronized
Jan 1st May 12th Source Changed

But what happens every time is the May 12th file writes over the Jan 1st copy and I end up with the corrupted May 12th Document

Because ViceVersa tracks every file on both the Source and the Target, I KNOW that at the least this should be a Conflict. I understand the May 12th file is newer, but the history shows that the change happened on the Source Drive and not the Target.

Sincerly
John