When we ran into DST issues, we had to take out the Time Zone value setting it to NULL. It actually in our case comes down to a MSFT dll that needs to be fixed. The Remedy User tools uses that dlls for some of it's date manipulations. We couldn't roll out the dll, because it would require us to test all our VB, etc apps. Just to much of a time eater, easier just to set the time zone in the user tool. As a side note, when this happened I checked in the database, and it was storing the dates correctly.
Randy -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Bean Sent: Wednesday, March 12, 2008 11:07 AM To: arslist@ARSLIST.ORG Subject: Re: DST - Leap Year Issue with Date Only fields Hi Michelle, I believe I encountered the same issue you are describing on a 5.01.02 AR Server back in 2006. I reported the issue to BMC Support, and the issue was closed with a defect (SW00220325). See attached for a copy of the issue. I never received any follow up on the defect (go figure), but when I looked it up today, this is what it shows: ID: SW00220325 Disposition: Verified Resolution: Not Reproducible Product: AR System Version: 6.00.01 Problem Area 1: Server Summary: I am running ARS 6.0.1 on a Windows 2000 Server. The server is set to automatically adjust for Daylights saving time. For the past two years on the day of the time change, the Date keyword renders the previous date. And on the next day at midnight The defect was submitted for another customer who encountered the same issue, so I am surprised that BMC was unable to reproduce it. I haven't tested to see if it has been corrected in ARS 7.0.1+. The issue seems to be related to the DST change, not leap year. --Thomas ----- Original Message ----- From: "Michelle L" <[EMAIL PROTECTED]> Newsgroups: gmane.comp.crm.arsystem.general To: <arslist@ARSLIST.ORG> Sent: Wednesday, March 12, 2008 10:28 AM Subject: DST - Leap Year Issue with Date Only fields > Hey Y'all: > > Remedy ARS 6.3 P23 (Server is in Central time zone) > Windows 2003 > SQL Server 2000 > Admin tool ARS 6.3 P23 > User Tool 6.3 P23 and 7.0.1 Patch 005 > > We're not sure if this issue is DST only related or DST and Leap Year > related. > > We discovered an interesting phenomenon when we reviewed records in > various > forms with Date fields (not Date/Time). On March 9, 2008 starting at 3:00 > AM and continuing through the remainder of the day, any Date field set > with > $DATE$ was set to March 8, 2008. It didn't matter what time of day it > was. > Date/Time fields were appropriately set to March 9, 2008 and current time. > > We had to update thousands of records in various forms. > > Did anyone who is still on Remedy ARS 6.3 experience this? > > Thanks, > Michelle > > > > ====================================================================== > > Confidentiality Notice: The information contained in and transmitted with > this communication is strictly confidential, is intended only for the use > of the intended recipient, and is the property of Countrywide Financial > Corporation or its affiliates and subsidiaries. If you are not the > intended recipient, you are hereby notified that any use of the > information contained in or transmitted with the communication or > dissemination, distribution, or copying of this communication is strictly > prohibited by law. If you have received this communication in error, > please immediately return this communication to the sender and delete the > original message and any copy of it in your possession. > > ====================================================================== > ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
