• It's going to be very interesting if the company ever adds extra readers. 😉

    We're talking about computers here and it always fascinates me that an IN/OUT reader system doesn't do a simple bit of checking. For example, an OUT punch should be rejected if there is no open IN punch. An IN punch should not be allowed if there are any other IN punches that are still open. Trying to reconcile double punches and missed punches is solving the wrong bloody problem. Someone needs to fix the read system so that it works correctly.

    If such a reader system is used to determine payroll, then trying to fix after-the-fact extra and missed punches is actually messing with people's pay. It's the reader system that needs to be fixed... not the reporting. The reporting is nothing more than a symptom of a bigger problem.

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