The file didn't change because it's not *.txt, it's *.log. Why aren't you using * instead of the multiple ??
Dawn Hast [email protected] wrote on 09/28/2009 12:07:54 PM: > I need a bit of help here and it is driving me crazy. I have a routine that > renames a file from 4632321214_0908221430.txt and I want it to change to > 4632321214_0908221430.ftp > > 1. These file name could be 10 to 40 char long > 2. I have NO control over the names (please do not ask me to change them) > > > I thought I had it covered and then 5 out of 60 would not accept the change. > I used the following: > RENAME ????????????????????????????????????????.txt > ????????????????????????????????????????.ftp (yes that is forty ??'s on > both sides) > > > > Example of a name that would not change: 104745_0909221430.log > > > I have a lot longer and shorter that did change names, all attributes are > "A" all local or network same results. Does not change from OS. No > difference between 7.6 or later, compiled or not. I suppose you could say, > "No green eggs or ham" trying to find humor! I have had this issue now for > three weeks and review a lot of old email trying to find my error. I do not > want to store a command (.cmd shell batch) and zip out or launch. I would > like this to stay internal, but I am also running out of options. > > Any thoughts? > > > > > Sincerely, > Paul Dewey > > DISCLAIMER: This electronic message together with any attachments is confidential. If you are not the intended recipient, do not copy, disclose or use the contents in any way. Please also advise us by return e-mail that you have received the message and then please destroy. Evergreen Packaging is not responsible for any changes made to this message and / or any attachments after sending by Evergreen Packaging. We use virus scanning software but exclude all liability for viruses or anything similar in this email or any attachment.
