With the network involved, it doesn't have to be the file that changed. Any temporary resource state in the fabric between you and the actual file could -- breifly -- manifest itself as in an inability to open the file.
That sounds frightening. I didn't expect this ... thought that in this case the underlying software layer (CIFS) would take care about such glitches. Just to get some idea ... what kind of resource state could, for example, cause such an effect?
I think I will follow your suggestion to do a retry....
Ronald Fischer <firstname.lastname@example.org>