It's not unknown for people to report that files that fail hash-comparison (which was the alarm bell that rang...) now won't open (in the appropriate app) but can still be copied fine (there's just now no point...). IIRC, I once had exactly that issue in another life with an Outlook PST. No sign of any CRC error from Windows, it just wouldn't open in Outlook. But it would copy fine (and overwrite previous backups ![:cry:]( "Crying or Very sad")
)
Anyhow, some good news (we hope). I understand we found a way (I suspect undocumented...) to tell the FTP component that we'll open and read the file instead of it, and that's what the dev dept have now done for the next release. So hopefully we'll now catch these kinds of errors before it takes over, but of course there's no way to test this for sure without corrupted drives/files to test it on.
No release ETA at this stage, but may be a beta beforehand. I'll make a mental note to jog your elbow if so.
)Anyhow, some good news (we hope). I understand we found a way (I suspect undocumented...) to tell the FTP component that we'll open and read the file instead of it, and that's what the dev dept have now done for the next release. So hopefully we'll now catch these kinds of errors before it takes over, but of course there's no way to test this for sure without corrupted drives/files to test it on.
No release ETA at this stage, but may be a beta beforehand. I'll make a mental note to jog your elbow if so.