[#1]

Has anyone had a problem with stash updating a newer file on a computer with an older file from another computer? this has happened twice to us with Micorsoft Access files. Not sure it hasn't happened with other file types. Anyfeed back would be appreciated.

[#2]

Do these older copies contain "conflicted copy" in their filenames?  Stash is built to deal with conflicts by modifying the names of the affected files and allowing for multiple copies.

Can you send us the log files from both computers?  Send them to stashbeta-support@mozy.com and I can have a look.  You can collect the log files together by right-clicking on the Stash icon in your systray, then select Help, then Collect Log Files...  Let us know in your email what file was involved in the conflict.

[#3 · Accepted solution]

As Kevin mentions this sounds like you may be hitting a conflict scenario.

A file can be edited on multiple machines, but its important that the changes synchronize before switching to a different machine.   So changing the file simulatenously or editing an older version of the file on an offline client can be problematic.  Database applications like Access can be particularly prone to conflict if they are ever opened/edited on more than one device at the same time.  Stash does not guarantee that the "newest" file takes priority in this sort of conflict scenario, but it does copy the file so that the conflict is more apparent and the two versions of the file are maintained.

-Andrew