Hi, Stephen: I did find a bug ID for the issue you addressed below. It is allegedly fixed in Mid-Tier 7.0.1 Patch 004. SW00266823 Certain dates, such as 11/01/2007, are corrupted on the Mid Tier. Thanks, Michelle
"Heider, Stephen" <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <arslist@ARSLIST.ORG> 11/02/2007 09:19 AM Please respond to arslist@ARSLIST.ORG To arslist@ARSLIST.ORG cc Subject Re: Possible DST Issue ** Michelle, I am not aware of any bug defect with this. Since this ?bug? will go away in 3 days anyways I hadn?t planned on submitting a bug report. BTW, because of the nature of dates and time changes, moving forward I plan to always set dates to character fields before sending to SQL. This way, it shouldn?t matter when the time changes. BTW #2, I recently read somewhere online that the Act that changed DST time in the US has a clause that allows Congress to revert back to the original DST time if they want to. When/if that happens then ARS, Java, OS?s and other programs will need to be modified once again. T-Shirt idea: Just say ?No? to Daylight Saving Time Stephen Remedy Skilled Professional From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Michelle L Sent: Friday, November 02, 2007 9:57 AM To: arslist@ARSLIST.ORG Subject: Re: Possible DST Issue ** Hi, Stephen: Thank you for the workaround and passing this along to the masses. Is there already a defect id for this? Thanks, Michelle "Heider, Stephen" <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <arslist@ARSLIST.ORG> 11/02/2007 07:37 AM Please respond to arslist@ARSLIST.ORG To arslist@ARSLIST.ORG cc Subject Re: Possible DST Issue ** Just wanted to pass this along? ARS 6.3 p22 (server, mid-tier, user tool), SQL Server 2000 (all patches), Windows Server 2003 (all patches). When passing a date in a date field within an active link to a Set Fields SQL User Defined Function Remedy changes the date to the previous day. This only occurs for dates starting this last Sunday through this coming Sunday. The work-around is to set the date field to a tmp character field first, then pass the tmp character field to the SQL user defined function. HTH Stephen Remedy Skilled Professional From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza Sent: Thursday, November 01, 2007 5:09 PM To: arslist@ARSLIST.ORG Subject: Re: Possible DST Issue Wow! That's weird. Does that happen from the native client too? Just for information purposes - what if you save it on the mid tier and then view the record from the mid-tier? What is the date displayed as? Also if you save from the native client does it display it correctly on the mid-tier? Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Suwanski, Ron Sent: Thursday, November 01, 2007 4:25 PM To: arslist@ARSLIST.ORG Subject: Re: Possible DST Issue ** Yes I saw it too.. but it was only for 11/1/2007. If you try 11/2/2007 it is fine.. From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Frank Caruso Sent: Thursday, November 01, 2007 12:51 PM To: arslist@ARSLIST.ORG Subject: Possible DST Issue ** ARS 6.3 p20 Solairs\Sybase MidTier p20 Apache\TomCat TZ:EST Have a form with a date (not date time) field. User enters the date 11/01/2007. When they save the record the MidTier is changing the date to 10/31/2007. I was not able to find any way of setting 11/1/2007 in that field. Also, if I enter the date as "11/1/2007 4:00:00 PM" it puts 11/0/2007 as the date. Anybody else seeing this scenario? Thank you Frank __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ ====================================================================== 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. ====================================================================== __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ ====================================================================== 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"
