thinking about the math, logged in - logged out is diff, so I would expect low numbers, perhaps the others are not getting a @diff.

Unless your meaning like this

I can explain the math. We are a call center, when one of our agents logs out. the TAS software saves to the logout db.

The time stamp is when they logged out. and then you use the field "logged in" which is the number of milliseconds they were logged in to figure out their start time.

Also the times tamp that they use is in minutes and it starts on the 30th of whatever year where as crystal starts on the 31st. So that is why logged in is the time stamp divided by 1440 (number of minutes in a day) + 1 day so that it outputs the correct date.

Numofmins is the number of minutes they were logged in. Again that DB field is in mili-seconds. hence dividing by 1000 to get seconds, then 60 for minutes.

There is no logged in field in the db. to figure that out you have to subtract logged in time from the timestamp when they logged in. hence that is why logged in is what it is.

as it turns out. For whatever reason on that date instead of using the last login datetime like it has every other time. It was using the first. so it was doing the calculation right, just used the wrong value. Just made a max field to get the maximum of loggedout and that fixes the problem and prevents it from reoccuring.