I suppose people don't use File Content comparison method?
Or don't use Excel?
Or don't use the two together?
And it's true.
Make a copy of an .xls file (ahead of time).
Open that Excel .xls file.
Do nothing more except close Excel.
Check the hashes of your back up & the "unchanged" just closed file.
:-).
(I don't use Excel, instead, Multiplan.)
Why with .xls files do I get the error 'Data change at file...'?
Unfortunately the Excel application does dirty tricks when handling .xls files, that may cause the followings data error:
Data change at file '/xxx/xxx.xls' at position '0'
WARNING! Unexpected data modification of a file without parity!
This happens because Excel modifies the files after opening them, even if you don't press 'Save'. It stores the name of the last user that opened it to be able to report if another user tries to open the same file at the same time. To avoid to have the file triggered as modified, it restores the time-stamp to its original value. But the file was modified, and SnapRAID reports it.
To workaround the problem you can see How to prevent Excel from modifying the file on exit?, or you can switch to the .xlsx format.
