Shop Calendar Working Days

mrQQ
mrQQ Member Posts: 239
edited 2006-11-20 in NAV/Navision Classic Client
Hello,

does anyone else find the way they are filled ridicuously illogical? I mean, seriously. 00:00:00 to 08:00:00 is NOT 8 hours. It is 8 hours and 1 second. So if I add 08:00:00 to 17:00:00 i have 2 work shifts working together for one second (08:00:00) one. Why have it like this???

:|

Comments

  • Quivelus
    Quivelus Member Posts: 24
    I suppose because the following:

    If you have integers 1 and 2, then 1..2 includes 2 numbers (namely 1 and 2), but the difference 2-1 is 1. So this are two different things. A day (24h) for example lasts from 00:00:00 untill 23:59:59 (and possible some extra milliseconds if you wish; or to be correct, the closing date for that particular date) and not from 00:00:00 until 00:00:00 (because this is the start of the next day).

    --> Second 00:00:00 is counted twice!
    Bohr-ing.
  • mrQQ
    mrQQ Member Posts: 239
    well i understand that, thats why i'm saying its not logical. so why is it so then?
  • mrQQ
    mrQQ Member Posts: 239
    actually, it's even worse, if i enter them like that i can't even calculate calendar properly!
  • Quivelus
    Quivelus Member Posts: 24
    next supposition :-]

    You can see time as number of seconds (milliseconds...). Let's look at it from the seconds point of view:

    So one day lasts 24*60*60 seconds (thus, if starting from second 0, until second 24*60*60 - 1). Next day starts at 24*60*60th second. Now 00:00:00 from day one stands for the second 0 (! this is important, it is not second 1), then 00:00:00 from the second day stands for second 24*60*60.

    Conclusion (24*60*60) - (24*60*60 - 1) = 1 second.

    If you are not helped by this, can you state what the purpose is, or what you are trying to do? These are the things i know, but perhaps your problem concerns some other matter? Can someone help us out?
    Bohr-ing.
  • mrQQ
    mrQQ Member Posts: 239
    its simple. help states that i should enter working time as

    monday 07:00:00 10:00:00 shiftA
    monday 10:00:00 13:00:00 shiftB
    monday 13:00:00 16:00:00 shiftC

    which I'm saying is NOT LOGICAL, because this way it means that both shift A and B are working on second 10:00:00, and both B and C are working on second 13:00:00. but fine, it can be so if they want it that way, but then it DOES NOT EVEN CALCULATE CALENDAR when used on SQL! it throws redundancy error. And even worse, if I fix that error, then if there is entry which says shift is working from 20:00:00 to 00:00:00 (midnight, remember, help tells us to enter times like that!), then i get negative capacities in calendar entries!
  • kine
    kine Member Posts: 12,562
    And they are not working 1 seconds together, but 0.999999 seconds... :-)
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • mrQQ
    mrQQ Member Posts: 239
    no, it's 1 second :) 1st of 10th hour.
  • themave
    themave Member Posts: 1,058
    So then does your time clock sound at 9:59:59 for the end of a shift and then again at 10:00:00 for the start of the next, I think not

    It sounds at 10:00:00 which is the end of one shift and the start of another, so for that fraction of a second they are both working.

    get a life, is this really a concern, just wondering

    David
  • mrQQ
    mrQQ Member Posts: 239
    yes, this *is* a concern, because you CANNOT use it properly at the moment, and that's what i'm asking about.

Categories