Hi all,
Our customer has a Sharp MX-3050N and scans via SMB to numerous different folders. When they scan, they give each file a name before scanning. Just recently, when they scan in a file with the same name, it does not get overwritten on the computer side.
For example, they scan a file and name it "test". It is scanned to the folder and appears as "test". A few days later, they scan again to the same directory and want to overwrite that old "test" file with this new "test" scan. When they scan it now, it does not overwrite the old file, but instead it is renamed to "test(1)". So both "test" (the old file) and "test(1)" (the newest scan) are in the folder.
This just started happening a few days ago. Previous to that, when they sent over the scan with the same file name, it would overwrite.
I'm guessing that this is a Windows OS setting that may have changed, as the appending of the (1) is how Windows handles it generally.
I did look on the copier and could find no settings that may cause this behavior. I tested scanning to a folder at the office (different copier) and it overwrote the old file properly, instead of creating a new, renamed one.
Any suggestions?
Thanks.
Our customer has a Sharp MX-3050N and scans via SMB to numerous different folders. When they scan, they give each file a name before scanning. Just recently, when they scan in a file with the same name, it does not get overwritten on the computer side.
For example, they scan a file and name it "test". It is scanned to the folder and appears as "test". A few days later, they scan again to the same directory and want to overwrite that old "test" file with this new "test" scan. When they scan it now, it does not overwrite the old file, but instead it is renamed to "test(1)". So both "test" (the old file) and "test(1)" (the newest scan) are in the folder.
This just started happening a few days ago. Previous to that, when they sent over the scan with the same file name, it would overwrite.
I'm guessing that this is a Windows OS setting that may have changed, as the appending of the (1) is how Windows handles it generally.
I did look on the copier and could find no settings that may cause this behavior. I tested scanning to a folder at the office (different copier) and it overwrote the old file properly, instead of creating a new, renamed one.
Any suggestions?
Thanks.
Comment