• dc.pc100 (9/30/2013)


    20130616.xlsx

    201307.xlsx

    HSE.201306.xlsx

    HSE.201307.xlsx

    2013 ICT Calendar.xls

    Inv.10017355.txt

    The big question would be... what do you want for the final file names for the file names above? I could guess on some of the more obvious ones but I hate guessing at things like this.

    Speaking of "naming conventions"... based on what you've requested, there are two problems here...

    1. The tail is wagging the dog. These files should be named following both a format and naming convention at the source instead of you having to write code to handle such things on the backend.

    2. You still don't have an actual naming convention because even the modified date can appear anywhere in the file name or could be totally missing as in that last example above.

    My recommendation would be to drop this task and use the file creation date, instead.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)