Hey arnelgp. Don't want to keep bothering because your help is great. The error does seem to be fixed unless I close the program and reopen several times the error reappears in report. I am testing doing occasional clock ins with no clock outs and testing report in between them. This is when the error happens. I know there may not be as many no clock outs as I am testing with but it only takes a few and I'm sure I'll see them.