Short Story: A file on my computer is disappearing when accessed by another user on the network.
Long Story: I have a partition on my computer (E:) that I share the root of on my work network. In the root directory, there is (was) a MapPoint file (E:/mapfile.ptm). Sometimes, when someone is using that file on a different computer and tries to save it, it shows this error:
"A file by this name already exists and is read-only or locked by some other means. In order to save it, type a different name."
However, even if you try to save as a different name or in a different location (including locally to the computer using the file), the same error comes up, and the file disappears from the file system on my computer.
This has happened multiple times. At first, I thought I had accidentally deleted the file myself. After 2 more times though, including a "now you see it, now you don't" experience today, I know it is not a user error from either party. My best guess is that restarting my computer is the root of the problem. I restarted while the file was open on the other computer, and I suppose when the other user tried to save, the file handler was confused since the network resource had been reset. I would expect this to lead to not being able to save a file, but deleting the file off of the shared drive makes no sense.
The file was open on the other computer when I restarted my computer this morning. After the error message on attempted save, I made sure the file still existed on my machine where it belonged, and it did appear in the file list. Moments later, after attempted save-as, the file does not show in the file list in explorer.
I started playing with it after that. I restarted my computer with the file open on the other computer. If I use Windows Explorer to view the networked drive before I try to save it, it seems to work fine. How is the file being deleted when the program thinks that it can't access the file?