• I've seen quite a few mistakes in temporal calculations. None of them were the direct result of adding a valid character based time to a DATETIME. I've seen it get the blame for human mistakes and human misunderstanding but I've never actually seen it to be the direct cause of a problem. I think that MS did us all a great disservice by removing the "direct" math capabilities on the other "newer" data-types. I'd have been quite happy if they had extended the "direct" math functionality to be more like EXCEL where you can add "times" (durations) in excess of 24 hours and have things work as expected.

    --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)