• On the other side of the same coin...

    I won't support change for the sake of change or for the sake of someone being a cool kid that just deployed the latest version of a rubber chicken. I've found that too many people simply can't resist the latest shiny object even if it has a negative ROI. That's not to be mistaken with the "we've never it done it that way" syndrome. If someone has got something good, they need show me that it's good (as in better than what we have) and I'll help them champion what ever it is. If they can't demonstrate that it's actually better, then it's just another rubber chicken and they need to calm the hell down until they can. 😉

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