• David.Poole (6/9/2015)


    For some reason I kept hearing "by the time a man thinks his father may have been right he has a son who thinks he's wrong".

    Back in the 1980s I had a young (though older than me) and enthusiastic business manager proclaim that IT staff were going to be obsolete because any clued up business person could do all that was necessary on a PC.

    The fastest way to learn what something does is to try and change it. Sometimes you just have to let them have their car crash.

    That's one of my favorite teaching methods for someone that has a hard time getting over themselves. "Give them the opportunity to fail". That should NEVER be confused with the backstabbing low-life method of setting someone up to fail. It means that if there's no danger to the data or the server, let them try their way and be there to kindly and thoughtfully pick them up and help them dust off when they fail. Yeah... it does sometimes take a fair bit of extra work that you might not have time for but I've made some rather powerful allies out of previous "enemies" that way. Most of the time, you only have to do it to someone once and most of the time, it's well worth it.

    And, to be sure, it might be a lesson learned for me because they might be right. 😉

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