L
lbour
Seemingly random temp files are appearing in a directory where I maintain
three excel files that are accessed by multiple users.
I have three excel files stored in a single directory on my company's
network. The files are accessed by Store Managers through our VPN via Citrix.
I update these files in the mornings, and Store Mgrs add their comments
throughout the day to sections relevant to their particular store.
For the past three weeks, when I access the directory to update the files,
there are up to 100 files that look like .tmp files. However, there are no
endings on the file names (e.g., C2D05100). If I sort by Type, they are all
together, but Type = File and not Tmp File like I would expect with a .tmp
file.
I can delete them easily enough... but I don't know why they are appearing.
I've maintained the three files in the same directory for over 9 months...
and this issue has just arisen in the past three weeks. I can't spot anything
different about the properties or options.
I've been told that it could be related to a recent MicroSoft update.
Any ideas?
Thanks,
Lee
three excel files that are accessed by multiple users.
I have three excel files stored in a single directory on my company's
network. The files are accessed by Store Managers through our VPN via Citrix.
I update these files in the mornings, and Store Mgrs add their comments
throughout the day to sections relevant to their particular store.
For the past three weeks, when I access the directory to update the files,
there are up to 100 files that look like .tmp files. However, there are no
endings on the file names (e.g., C2D05100). If I sort by Type, they are all
together, but Type = File and not Tmp File like I would expect with a .tmp
file.
I can delete them easily enough... but I don't know why they are appearing.
I've maintained the three files in the same directory for over 9 months...
and this issue has just arisen in the past three weeks. I can't spot anything
different about the properties or options.
I've been told that it could be related to a recent MicroSoft update.
Any ideas?
Thanks,
Lee