• herladygeekedness (10/31/2013)


    Facts will always be on your side.

    Were I you, I would make darned sure of what the processes currently do, and how they are done, in order that you can confidently state How It Works Now, and hopefully be able to get to "How It Should Work."

    Try to ignore the drama and dedicate yourself to the business at hand. Take a deep breath and dive in, documenting the crap out of it.

    You cannot control anyone, you can only control how you react to them, so stay on the side of professional business and you should be fine.

    If that all fails, just remember that you were looking for a job when you found that one. You have marketable skills and it is your choice as to where to utilize them. Hopefully it won't come to that, but there are difficult people in the world. Some are worth working with, others are not.

    I read the OP's post and was getting ready to reply when I saw your's. I couldn't have said it any better.

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