OK, I will try to explain this as best I can.

We have a Timecard system built in FileMaker. Our HR department had us build in some "exceptions." At our offices, weekend are always paid at the overtime rate. So in the system, they(HR) wanted us to program the system so that if a person started their shift on a Friday at 8PM and worked until 3AM Saturday morning, when they punched out for the day, the Friday hours would show 8PM to 11:59PM, and then a Saturday punch would be added that showed 12AM to 3AM.

We have this deployed at 4 divisions, and we only have a problem with one. The past few months, they have a guy who has been coming in on Saturday at about 5AM, and leaving anywhere between 9 and 11:30Am. When he punches out, it treats it as if he has crossed days.

They are on the most recent versions of all software(Server and Client) and we have narrowed it down to one statement but we cannot figure out what about the statement evaluates, i guess, incorrectly.

the statement is

GetAsDate ( Get ( CurrentHostTimeStamp ) ) ≠ GetAsDate(PunchIn_Serial_Timesheets::Date)

where PunchIn_Serial_Timesheets::Date is a date field ( I know the get as date seems redundant, but it was added to make sure FM was seeing it as a date. PunchIn_Serial_Timesheets::Date is a field in a portal that we loop through while checking other things.

Any Ideas as to why this would evaluate to true when both dates are the same?

Edited July 2, 200718 yr by Guest

"PunchIn_Serial_Timesheets :Date is a field in a portal"

Make sure that the process isn't just seeing the first related record.

Copy and paste each side of the equation into the data viewer and see how it evaluates. That's always a good place to begin when troubleshooting this sort of thing.

Thanks or the responses.

We have done all sorts of debugging on this thing. From Dialogs of the two dates(which do show they equal) to extra fields.

They all evaluate as equal, but the stuff inside the if statement still gets executed.

Is there a different way I can test that same scenario that might be a bit more reliable?

The client machine wouldn't by chance be in a different time zone?

Nope. They are both in the same time zone(literally and time/date settings)