• Ed Wagner (7/30/2015)


    I forgot to add it to the article, but many thanks to Jeff Moden for being my reviewer, giving me good advice and encouraging me to write it in the first place.

    I don't feel slighted in the least, Ed. In fact, IIRC, since it's your very first article, I believe I suggested just leaving any credits for those things off. This is a complex article for a "beginning writer" and you did a great job.

    Shifting gears a bit, I agree that there are many ways to skin this particular cat. But to emphasize the background that Ed tried to portray in his article, Ed basically had no budget for this problem and he had to do it quickly because of management demands based, supposedly, on some urgent customer related demands so there wasn't much time to explore different avenues even if they were free. When I say "quickly", I mean virtually "overnight". The reporting was also a critical feature according to management. The article is a great testimony and documentary to the idea that "Before you can think outside the box, you must first realize... you're in a box". 🙂 Since the company was already using Ultra-Edit for other things, it also shows some great innovation without introducing more to the proverbial "Tower of Babel" that so many companies suffer.

    Even better than that, management didn't think he could actually pull it off without buying something else and they certainly didn't think he could pull it off virtually "overnight" even if he were to buy something to help.

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