If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Re: scan to smb same file name replaces earlier file?
Originally posted by Darren King
Huh?
Ok, you're scanning to a pc folder, you give the file a name such as "test", then, you do another scan and give the file the same name "test". The 2nd file replaces the 1st.
U would think windows would show : test.pdf(1) & test.pdf(2)
But it doesn't, only the 2nd scanned file is present.
I know, it sounds crazy, but I've seen it twice now. Just looking to see if anyone else has.
Re: scan to smb same file name replaces earlier file?
Makes sense...if you use the default name, then each file would be different as the date/time would be off from scan to scan...but if you rename each doc "test" then the new "test" would overwrite..You would see a pop up on your screen if you were moving this manually, but the MFP can't interact with the folder, only write to it...But to be sure, I will test this on one of our demo MFPs and see if I get the same results. Emujo
If you don't see your question answered in the forum, please don't think it's OK to PM me for a personal reply...I do not give out firmware and/or manuals.
Re: scan to smb same file name replaces earlier file?
Windows won't allow two files with the same name.
If you want them to be "test1" and "test2" you will have to call them that before you send them.
Darren
Re: scan to smb same file name replaces earlier file?
I tested it and got the same results...but, there is a solution...KM offers special firmware that will add a 0-9 to any scanned (SMB) documents that are scanned within the same min..Your default name will now be SKMBTC360101112093501/02/03 ect until the minute increments and the process starts over again. If you're a KM tech search the knowledge base for "default scan file name" and you will see it. If you're not a KM tech you are out of luck. PS this will only work if the customer is using the default scan name. Emujo
If you don't see your question answered in the forum, please don't think it's OK to PM me for a personal reply...I do not give out firmware and/or manuals.
Re: scan to smb same file name replaces earlier file?
This same issue came up on Kyocera products. It names the resulting PDF files with a date/time stamp or sequentially, so there are never duplicate file names. We had this same issue with Virtual Mailboxes. If you send the same print job ten times and all the files have the same name each job after the first over-writes the previous. Same fix. =^..^=
If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
Re: scan to smb same file name replaces earlier file?
Looks like you have your answers, but here are another few thoughts/workarounds:
Well it seems to me that it would be easy enough to change the file name every time, or do a batch scan if applicable.
Or you can change the names on the computer manually after each scan
Or...cut/paste into a different directory after each scan and do that "copy and keep both" or something like that.
Also, the other thing you could do if you are feeling adventurous is find/create a script to automatically do this for you every few seconds or so.
I did a quick Google Search and found this (but I am on campus and cannot test it).
This would actually be better than the patch if you are looking to do more than 10 consecutive scans at a time (that is, if I understood emujo correctly).
Re: scan to smb same file name replaces earlier file?
Thanks guys, I know it's a petty problem. Just renaming the scan once it's in your folder should be good enough... but we know how some customers can be...
And I was expecting to see the (1), (2), after each file...
The fact that the copier can't interact with the folder (only write to it) is the explanation that I'm sure my customer will understand, thanks Emujo!
Comment