> The original issue noted that it was happening only in an Excel host, not Access. That has now changed - I'm having it happen _very_ consistently in Access now, too.
I'm working on my laptop connected via VPN to the corporate network. That should _not_ however, have any impact on the situation, since the file is being written to/read from a _local_ directory on my physically present C: drive (i.e., there is no magic mapping that I'm aware of going on in the background). For example:
```