• The other issue is of a huge concern and generally a huge PITA for users and that can all be described in a simple, very well worn statement...

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

    My favorite example is the "Ribbon Bar" in Microsoft Office.  Such a thing was a great idea but it now takes many more (totally unnecessary) clicks to do many common tasks never mind actually finding the correct ribbon to use for a task because certain functionality actually seems to be on the wrong ribbon.

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