> The Server team has patched the Server as well. > I have added my TimeZone to my User Preferences, taken it off and that did not make any difference.
You don't mention whether your clients have been patched for DST. Keep in mind that the Mid-Tier uses internal libraries to determine DST, but the client will use the operating system - or the 'C'-Run-Time (CRT) libraries if you have a specific time zone set as a preference (or have the TZ variable set in the OS). Check out a description of how this affects historical dates in the following tech bulletin for AR System 7.0.01: http://www.bmc.com/supportu/documents/87/89/68789/68789.pdf You may be encountering a similar issue where the client is performing an incorrect DST calculation and writing the information incorrectly to the DB. The Mid-Tier is properly displaying this incorrect information. When you view it again in the client, the client does the same "bad" conversion back to the correct time. The tech bulletin shows this process graphically... Perhaps not the issue you're seeing - but I would still check to see if your WUT client operating systems have been updated with a DST fix of some sort - either the Microsoft OS Registry patch or the updated CRT libraries if you're using TZ. -David J. Easter Sr. Product Manager, Service Management Business Unit BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Perrault Sent: Friday, March 23, 2007 10:21 AM To: arslist@ARSLIST.ORG Subject: DST Date/Time in a Table field on the Web Error All, Environment: AR User: 7.0.00 Patch 001 AR Server: 7.0.01 Patch 001 200701111654 Mid-Tier: 7.0.00 Patch 001 200605201549 Java JRE: 1.4.2 Patch 13 IIS Windows 2K MS-SQL Ok, I've got a Join-form with a Date/Time field on it. I created a record on one of the base forms after the DST change/patches. When I open the Form in the User too, the Date/Time field shows the correct time. Yet when I open the Join Form on the Web the Date/Time field in the Results List table at the top shows the time off by an hour (1 Hour back). For Example the value in the field on the base form as well as the Join-form, when opened in the User Tool shows: 3/16/2007 10:32:44 AM When opened in the Web, the Column in the Results List table field shows: 3/16/2007 9:32:44 AM I've checked the Registry entries on the Server and they look good. The Mid-Tier runs on the same server as the ARS Service and the time on the Server looks good. The Server team has patched the Server as well. We've tested the Java Engine, and that appears ok, and DST compliant. I have added my TimeZone to my User Preferences, taken it off and that did not make any difference. The strange thing is, that records that were created before the DST time change show the correct Date/Time in both the User and Web. Records created AFTER the DST patch show the time off by an hour. The Mid-Tier and AR Server are both in the same time-zone as I am. So my questions are: 1) What could be causing this? 2) Is anyone else experiencing this? 3) Any Suggestions on how to fix this or where to look? Thanks, Matt ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
