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.
is pronounced ree-bar and is a Modenism for R
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.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is usually not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs