I don’t blame you. This sounds very puzzling.
That means the file on the server was not corrupted. When you open a file, Panorama immediately checks it as soon as it lands in memory. If it is corrupted, Panorama rejects the file, it flushes it from memory, the windows don’t open, and an error is reported. So if no error is reported, the file is ok.
This indicates that the corruption happened on your computer, after the file was opened (because we know it was ok when loaded into memory).
Don’t know, and maybe it isn’t the cause, but somehow the file had to change between when it was opened and when you pressed Command-Save. There are only two steps that happen during that period that I can think of.
- The file is synchronized with the server.
- The .Initialize procedure runs.
Of course, the third option is that there is a hardware problem, but since this happened multiple times and only with this one file, that seems very unlikely.
Hmm, on further reflection, since you downloaded a fresh copy of the file from the server, the synchronization step should not do anything, since the file would already be 100% synchronized.
I agree on the highly likely part, and the “don’t know which way” part also. Actually, if corruption every happens I don’t know how, since if I did I would just fix that part of the program. Ideally corruption should only happen if a cosmic ray bonks your memory chip or a magnetic field zaps your hard drive (not sure about what the failure modes for SSDs are).