I have a database that tracks PTO time. When someone puts in a request, it counts the number of people off on that day (using a document collection from a view), and only allows the time off if that day hasn’t hit maximum.
Here’s the problem … there are 3 people off (the maximum) on 3/13/2008, but only 1 on 3/14/2008. However, nobody can request time off for 3/14/2008 because for some reason the view is seeing the 3/13/2008 date and counting that. I know this because I added some msgbox’s to the script to tell me what it’s seeing.
Here’s the rub - it is only happening on the server replica that is housed in Phoenix. As long as we use the local replicas, it works fine … so I’m guessing it has something to do with the time change. For now, I am telling everyone to use their local replicas … but wanted to find out if there was anything I could do to correct it.
I have already put this formula in the Date column in the view it is looking at, which I thought would fix it:
@Date (@TextToTime (@Text (StartDate ; “D0S0”)))
ALSO - I don’t have access to server administration, but if there’s something I need to tell them to do, I can …
THANKS!
Subject: RESOLVED - More Daylight Savings Time Issues
I found this technote that goes against everything I ever thought - apparently having a date only field can CAUSE these issues, so you should default the time to SOMETHING, even if you aren’t going to use it. The example defaults it to 1AM - but because I need to make sure that the document falls in the view on the right date all over, I defaulted it to 6PM.
http://www-1.ibm.com/support/docview.wss?uid=swg21105140
Subject: RE: RESOLVED - More Daylight Savings Time Issues
We just encountered the same thing today. I @Adjusted the field by 1 hour & 1 minute to make it (date) 1:01:00 AM in the view column. It worked fine and should still work after DST is over.
Subject: More Daylight Savings Time Issues
Hey Tony,
I’m wondering if it’s the server. I have scheduled agents running and the time frame on the servers are off by and hour. I’m thinking that you will need to contact the admins for the server and get them to run the DST patch, which should hopefully resolve your issue.
Edmound
Subject: More Daylight Savings Time Issues
Toni, are all the people entering the bookings located in the same location?
What are you storing in the document? (Date only, date/time, string or Date?)
Here is how you could run into a problem.
Let’s say you;re storing a full notesdatetime when someone books a day off.
ff I book 2008-03-12 off and it store 2008-03-12 12:00am EDT the someone in Californa looks to see if they can take the 12th of will see no one else has asked for the 12th off because it will look like I’ve got 2003-03-11 9:00pm PDT.
Therefore you need to make sure you are comparing the samething.
Three booking made for 2008-03-13 12:00am MDT would look like three bookings for 2008-03-14 (2am) EDT.
Subject: RE: More Daylight Savings Time Issues
The document is storing a date only … and the view is looking at what was in the original post. The thing is, this didn’t start happening until after we changed the clock.
Most of the people entering time are in Houston, TX (Central time) … a couple in Canada (Eastern time), me in Michigan (Eastern time) and one in New Jersey (Eastern time). The agent, however, runs on the server, which is located in Phoenix, AZ.
I’ll see if I can get hold of someone in PHX and see if they’ve run the DST patch … in the meantime, I’m going to test and see if everyone can just use their local replica. That seems to be working.