Making a database with shifts people work. I need the ability to have them span nights. so i have a date start and end field and a time start and end field. I made a calculation startcalc and endcalc that is a timestamp so i could have one field to reference for relations. I have a relationship to another occurrence to check for overleaping records like this

ID != ID

startcalc < endcalc

endcalc > startcalc

this was working and without being aware of why it now doesn't is there something funny with timestamp fields or something i am not getting here??

I don't follow why you need to use the timestamp in a relationship. "Overleaping" records are those that span more than a day, yes? Couldn't you just create a calc that'll tell you if the difference btw the enddate and startdate represents at least 1 day?

I think they meant "overlapping" - at least that's what the described relationship would do.

However, there's not much one can say when all we know that "it was working and now it doesn't".

just wondering if there is some kind of limitation on the amount of calculation fields or something like that. I hate to start going backwards until it starts to work

and yes i ment overlapping