Daylight saving time causes a date error on 01/APR

morning dears,
we are facing an issue related to Daylight saving time, as the following:
at any page on the system that contains a calendar if we choose the date 01/04/2012 it generate an error...
example on this error :
on Leave Request page --> when choosing 01/04/2012 then clicking on calculate duration-->
01/04/2012 is not a valid date. Please re-enter.
any suggestions??

dears any suggestions to solve the issue??
have anyone faced this before?

Similar Messages

Conversion mapping is losing time zone data during daylight saving time

We have a problem with conversion of Calendars to timestamp with timezone for the last hour of Daylight Saving Time (e.g. 01:00 EDT - 01:59 EDT) where it is being interpreted as Standard Time which is in reality 60 minutes later.
We've written a JUnit test case that runs directly against TopLink to avoid any issues with WAS and its connection pooling.
The Calendar theDateTime comes from an object called TimeEntry which is mapped to a TIMESTAMP WITH TIMEZONE field using conversion mapping with Data Type TIMESTAMPTZ (oracle.sql) and Attribute Type Calendar (java.util).
We are using:
Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build Patch for Bugs 5145690 and 5156075)
Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
Oracle JDBC driver Version: 10.2.0.1.0
platform=>Oracle9Platform
Execute this Java:
SimpleDateFormat format = new SimpleDateFormat("MM/dd/yyyy HH:mm z");
TimeZone tzEasternRegion = TimeZone.getTimeZone("US/Eastern");
Calendar theDateTime = Calendar.getInstance(tzEasternRegion);
theDateTime.setTime(format.parse("10/29/2006 01:00 EDT"));
Persist to the database and execute this SQL:
SELECT the_date_time, EXTRACT(TIMEZONE_REGION FROM the_date_time), EXTRACT(TIMEZONE_ABBR FROM the_date_time), EXTRACT(TIMEZONE_HOUR FROM the_date_time)
FROM time_table WHERE time_table_id=1
This provides the following results:
THE_DATE_TIME EXTRACT(TIMEZONE_REGION FROM the_date_time) EXTRACT(TIMEZONE_ABBR FROM the_date_time) EXTRACT(TIMEZONE_HOUR FROM the_date_time)
29-OCT-06 01.00.00.000000 AM US/EASTERN US/Eastern EST -5
The wrong time zone is in the database. It should be EDT -4. Let's test the SQL that should be generated by TopLink. It should look like the following.
Execute this SQL:
UPDATE time_table SET the_date_time = TO_TIMESTAMP_TZ('10/29/2006 01:00 US/Eastern','mm/dd/yyyy HH24:MI TZR') WHERE (time_table_id=1)
SELECT the_date_time, EXTRACT(TIMEZONE_REGION FROM the_date_time), EXTRACT(TIMEZONE_ABBR FROM the_date_time), EXTRACT(TIMEZONE_HOUR FROM the_date_time)
FROM time_table WHERE time_table_id=1
This provides the same results:
THE_DATE_TIME EXTRACT(TIMEZONE_REGION FROM the_date_time) EXTRACT(TIMEZONE_ABBR FROM the_date_time) EXTRACT(TIMEZONE_HOUR FROM the_date_time)
29-OCT-06 01.00.00.000000 AM US/EASTERN US/Eastern EST -5
Now, execute this SQL:
UPDATE time_table SET the_date_time = TO_TIMESTAMP_TZ('10/29/2006 01:00 EDT US/Eastern','mm/dd/yyyy HH24:MI TZD TZR') WHERE (time_table_id=1)
SELECT the_date_time, EXTRACT(TIMEZONE_REGION FROM the_date_time), EXTRACT(TIMEZONE_ABBR FROM the_date_time), EXTRACT(TIMEZONE_HOUR FROM the_date_time)
FROM time_table WHERE time_table_id=1
This provides better results:
THE_DATE_TIME EXTRACT(TIMEZONE_REGION FROM the_date_time) EXTRACT(TIMEZONE_ABBR FROM the_date_time) EXTRACT(TIMEZONE_HOUR FROM the_date_time)
29-OCT-06 01.00.00.000000 AM US/EASTERN US/Eastern EDT -4
The correct time zone is now in the database. Let's test reading this with the following Java:
System.out.println("cal= " + theDateTime);
System.out.println("date= " + theDateTime.getTime());
System.out.println("millis= " + theDateTime.getTimeInMillis());
System.out.println("zone= " + theDateTime.getTimeZone());
This provides the following results:
cal= java.util.GregorianCalendar[...]
date= Sun Oct 29 01:00:00 EST 2006
millis= 1162101600000
zone= sun.util.calendar.ZoneInfo[id="US/Eastern",...]
The TimeZone object is correct since we are using the US/Eastern regional time zone, but the millis are wrong which makes the time EST instead of EDT. The millis should be 1162098000000.
The conversion from java.util.Calendar to TIMESTAMPTZ loses the actual offset when setting to a regional time zone. It can maintain this info by specifying it explicitly.
The conversion from TIMSTAMPTZ to java.util.Calendar also loses the actual offset even if the correct offset is in the database.
Has anyone else encountered this conversion problem? It appears to be a conversion problem in both directions. I know that the Calendar is lenient by default and will assume Standard Time if time is entered during the repeated 1 o'clock hour at the end of Daylight Saving Time, but the Calendars we are using are explicit in their time, so this would be classified as data corruption.
Nik

Opened an SR. Looks like there is a problem with conversion either in TopLink or in JDBC.

BO-XI R2 daylight saving time

The time in infoview has not changed to accommodate the daylight saving time change.
Version: 11.5.8.8265
Tried to install xir2 edst patch (CHF15_DST), when doing so I get a message stating "MHF1 is needed as prerequisite"...when I try to install MHF1, receive message "No supported XIR2 products detected"
Please advice, thank you.

Symptom
The Integration Kit for Baan driver displays incorrect time data in reports. The time is off by an hour between the dates marking the old Daylight Saving Time (DST) and the new DST change.
Cause
DST has been changed to occur earlier in the year. The Integration Kit for Baan does not pick the new settings up.
Resolution
There are files called ZONEFILES on the BAAN Server. These files must be already updated on the Baan server side.
The Integration Kit for Baan installs our own version of these files in the following folder:
\Baan\Native\lib\ZONEINFO
on the hard drive where the Integration Kit is installed.
Back up these files on the Crystal Reports/Business Objects XI computer, then put a copy of the ZONEFILES from the Baan Server to the computer where the Integration Kit for Baan is installed.

When there is no daylight saving, i am facing an error

Hello , I have created an add in for outlook, we setup meeting rooms, we
opened mailbox for each meeting room. Users are using Outlook 2010. We can now see all meeting rooms in our calender. And we are able to set up meetings with corresponding meeting rooms. The only issue I need to fix is that : When someone organize a meeting
in with other countries; as Australia, France, Korea , China.. some of these countries don't have daylight saving and when changing my local machine time to korea for example, it gives me an error.
This is a part of the code where getting the timeZone , plz help me to know what to change for coutries that don't have daylight saving.
// Make the request.
GetUserAvailabilityRequestType request = new GetUserAvailabilityRequestType();
// Get the local time zone
TimeZoneInfo zone = TimeZoneInfo.Local;
TimeZoneInfo.AdjustmentRule[] adjustmentRules = zone.GetAdjustmentRules();
string str_offset = "";
TimeZoneInfo.ClearCachedData();
TimeSpan offset = TimeZoneInfo.Local.BaseUtcOffset;
if (offset.ToString().Substring(0, 1).Equals("-"))
str_offset = offset.ToString().Substring(0, 3);
else
str_offset = offset.ToString().Substring(0, 2);
// Set the time zone of the request.
request.TimeZone = new SerializableTimeZone();
//TimeZoneInfo.BaseUtcOffset Property
//Gets the time difference between the current time zone's standard time and Coordinated Universal Time (UTC).
request.TimeZone.Bias = (int)TimeZoneInfo.Local.BaseUtcOffset.Negate().TotalMinutes;
for (int iAdjustment = 0; iAdjustment < adjustmentRules.Length; iAdjustment++)
if (DateTime.Now >= adjustmentRules[iAdjustment].DateStart && DateTime.Now <= adjustmentRules[iAdjustment].DateEnd)
request.TimeZone.StandardTime = new SerializableTimeZoneTime();
request.TimeZone.StandardTime.Bias = 0;
request.TimeZone.StandardTime.DayOfWeek = adjustmentRules[iAdjustment].DaylightTransitionEnd.DayOfWeek.ToString();
request.TimeZone.StandardTime.DayOrder = (short)adjustmentRules[iAdjustment].DaylightTransitionEnd.Week;
request.TimeZone.StandardTime.Month = (short)adjustmentRules[iAdjustment].DaylightTransitionEnd.Month;
request.TimeZone.StandardTime.Time = adjustmentRules[iAdjustment].DaylightTransitionEnd.TimeOfDay.ToString("HH:mm:ss");
request.TimeZone.DaylightTime = new SerializableTimeZoneTime();
//TimeZoneInfo.AdjustmentRule.DaylightDelta Property
//Gets the amount of time that is required to form the time zone's daylight saving time. This amount of time is added to the time zone's offset from
Coordinated Universal Time (UTC).
request.TimeZone.DaylightTime.Bias = (int)adjustmentRules[iAdjustment].DaylightDelta.Negate().TotalMinutes;
request.TimeZone.DaylightTime.DayOfWeek = adjustmentRules[iAdjustment].DaylightTransitionStart.DayOfWeek.ToString();
request.TimeZone.DaylightTime.DayOrder = (short)adjustmentRules[iAdjustment].DaylightTransitionStart.Week;
request.TimeZone.DaylightTime.Month = (short)adjustmentRules[iAdjustment].DaylightTransitionStart.Month;
request.TimeZone.DaylightTime.Time = adjustmentRules[iAdjustment].DaylightTransitionStart.TimeOfDay.ToString("HH:mm:ss");
// Add the mailboxes to the request.
request.MailboxDataArray = mailboxes;
// Add the free/busy view options to the request.
request.FreeBusyViewOptions = fbViewOptions;
DateTime startExchange = DateTime.Now;
// Send the request and get the response.
GetUserAvailabilityResponseType response = esb.GetUserAvailability(request);
DateTime endExchange = DateTime.Now;
TimeSpan timeWSE2010 = endExchange - startExchange;
CLogger.WriteLog(ELogLevel.INFO, "getListRoomsExchange2010 -timeWSE2010-WS=" + timeWSE2010.ToString());
// Access free/busy information.
if (response.FreeBusyResponseArray.Length < 1)
MessageBox.Show("An error occurred while getting the available rooms - No free/busy response data available.", "Pick A Room");
CLogger.WriteLog(ELogLevel.ERROR, "GetUserAvailability - An error occurred while getting the available rooms - No free/busy response data available.");
else
for (int j = 0; j < response.FreeBusyResponseArray.Length; j++)
FreeBusyResponseType fbrt = response.FreeBusyResponseArray[j];
if (fbrt.ResponseMessage.ResponseClass == ResponseClassType.Error)
Console.WriteLine(string.Format("Error: {0}", fbrt.ResponseMessage.MessageText));
else
//Get the free/busy data
FreeBusyView fbv = fbrt.FreeBusyView;
if (!fbv.MergedFreeBusy.Contains("2") && !mailboxes[j].Email.Address.ToString().Equals(""))
availableUsers = availableUsers + ThisAddIn.dictionaryRooms[mailboxes[j].Email.Address.ToString()] + ";";
catch (Exception ex)
//Error processing.
MessageBox.Show("An error occurred while getting the available rooms - Exception:" + ex.Message, "Pick A Room");
CLogger.WriteLog(ELogLevel.ERROR, "getUserAvailability - An error occurred while getting the available rooms - Exception:" + ex.Message);
return availableUsers;

Hi,
Please post the detailed error message, it’s more helpful for further troubleshooting.
Since the add-in is related to Outlook client, I recommend contact Outlook for Developers Team so that you can get more professional suggestion.
For your convenience:
https://social.msdn.microsoft.com/Forums/en-US/home?forum=outlookdev&filter=alltypes&brandIgnore=True&sort=relevancedesc&filter=alltypes&searchTerm=
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

No daylight-saving time auto-adjust?

Using a Lumia 800 in the UK and (believe it or not) only just realised that it hasn't auto-corrected for daylight-saving time. Can't see an option for it either - am I just missing a really obvious setting somewhere? Time/date has many place options but no DST - is that correct?
Solved!
Go to Solution.

I think my experience may help.
I have had hours and hours of frustration with syncing my phone with Outlook calendar because of the way the date and time settings are described on my Nokia phone.
My Timezone is GMT+10 regardless of whether my location is currently in Daylight Saving. The automatic Daylight Saving settings on my computer adjust the time setting by plus 1 hour when Daylight Saving starts.
On the phone, however, setting the time works in a totally weird way. To get the right time on calendar events synced from my computer, I have to set up the phone according to the actual GMT time difference on the day I do the settings. Right now I'm in Daylight Saving so I have to put my Timezone as GMT+11. If I was doing the settings in mid-winter I would have to set the Timezone as GMT+10.
I just discovered this solution today! What a relief. My calendar events now appear at the same time on my phone as on the computer!
However, the whole Nokia time setup arrangement is quite incorrect and that explains the extremely long sequence of complaints on these discussion pages - going back to at least 2004.
It's very straightforward. My Timezone is GMT+10: it's GMT+10 in midsummer and it's GMT+10 in midwinter. A Daylight Saving adjustment doesn't ever change anyone's Timezone.
If Nokia used the correct meaning of Timezone, no-one would be having any problems with syncing events from their computer to their phone.
I have contacted Nokia separately about their serious error in misunderstanding the meaning of Timezone.

Brazil Daylight Saving Time Problem

In Brazil, we enter the summer time and my blackberry 9800 torch automatically work, but when I synchronized with the playbook, some problems arose.
The time in the menu setting is correct, as you can see in this image:
But the wrong time remains the main screen:
Does anyone have the same problem and knows how to fix it?
tks,

It did not work.
It is indifferent to select manual or automatic, the problem persists.
I'm in Brazil and with the correct time zone, but we are on daylight saving time.
On the menu setting time and date, the time is right, however, in early 1 hour on application clock and and late 1 hour on the main screen.

Daylight Saving Time Changes in 2007 for USA

Can anyone give me solution how to handle Daylight saving Time changes in 2007 in USA for JDK 1.3.x releases? We are using this due to some vendor dependency. We can�t upgrade to higher versions up to middle of the 2007. I would be thankful if somebody gets back to me.

I have a similar issue where we cannot upgrade the jdk 1.1 without involving a lot of effort. If we keep the same old jdk, can someone tell me if use of Date and Calendar api will be impacted by the Daylight saving change.....provided the timezone is default and not explicitly set to EST. Also there isnt any timezone related buss logic.

CreateODBCDateTime monkeys with Daylight Saving Time!!

If one uses CreateODBCDateTime to convert a date into the
proper format for storing in a SQL Server database, and one runs
this operation on a date between 0200 and 0300 on the day that
Daylight Saving Time changes, the function will change the time
forward or backward one hour. IT WILL DO THIS EVEN IF THE DATE YOU
ARE STORING IS UTC, thus rendering UTC times INVALID because they
do not have DST. Why does this function monkey with DST at all?

I have several international web sites on this server, one of
which has over 100,000 users who have contributed over 70 million
records, all with UTC timestamps. The problem occurs during the one
hour period EVERY YEAR when daylight saving time is started. It
does not do this in the fall when the time reverts. So, yes, the
problem only occurs during 1 hour out of 8,760 hours, but when you
start with 70 million records over 5 or 6 years...
But the danger is for anybody who stores or manipulates a
date/time OTHER THAN the date/time that is being used internally to
the server. In other words, if your server is set to Central Time,
and you have users in Hawaii or Arizona who need to store their own
date/time, it is likely to apply Central Timezone RULES to that
date/time, even if Hawaii and Arizona don't use DST.
Let's say you're scheduling operating rooms in a hospital in
Honolulu. All the CF routines are going to make sure to shift those
times forward an hour without warning, have a nice day. In my case,
it is happening with UTC, but it could be ANY time zone that has
different rules than the ones on your server.
Yes, I can probably figure out a different way to process
times, but this is a massive system with thousands of different
templates. In fact it affects several pretty massive software
systems with millions of lines of code, so it's not as if I can
just change a few SQL queries and be done with it.
It probably should be a rule for anybody operating a
ColdFusion server in an international setting, where dates and
times from different regions might need to be stored in a database,
to set up the server on UTC time just to avoid this problem.
Me, I have to
a. find all the places this will affect in thousands of lines
of code,
b. try to decide what impact going to UTC on the server will
have on things like scheduled tasks, email servers, etc,
c. then figure out whether there is any way to repair tens of
thousands of corrupted records

Support for US Daylight Saving Time changes in 2007

The Start and Stop dates for Daylight Savings Time in US will change from 2007.
From Sun's bug database, it looks like Sun has handled this Daylight Saving Time changes in JDK 1.5.0_06.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6317178
Does anyone know if they have handled this in earlier JDK releases (1.3.x, 1.4.x)? If not, do they have any plan to handle these changes?

1.3.1_18 had a timezone change.
http://java.sun.com/j2se/1.3/ReleaseNotes.html
1.4.2_11 had some timezone changes (but now there is a 1.4.2_12, so use that).
http://java.sun.com/j2se/1.4.2/ReleaseNotes.html
Not sure exactly what the timezone changes were, but check the release notes or give those JDKs a try.

Oracle Fix for U.S. Daylight Saving Time Changes in 2007

Hi --
Does any one know that if Oracle 10g Application Server (9.0.4) or Oracle 10g Application Server (10.1.2) as a fix for this issue.
Summary of the Issue: Information about the impact of the US Energy Policy Act of 2005, which changes the effective dates of US Daylight Saving Time (DST) in 2007 for the US. The passage of the Energy Policy Act of 2005 alters the Daylight Saving Time (DST) start and stop dates by four weeks. Extended Daylight Saving Time will begin in March of 2007.
The details for the issue can found at this location:
http://java.sun.com/developer/technicalArticles/Intl/USDST/
Thanks

Hi,
Thanks for posting.
Metalink Note:403311.1 for DST E-Business Suite (EBS))Patches.
Regards,
Phani.K

UC560 Daylight Saving Time

Hello,
We have a UC560. Once Daylight Saving Time (DST) was initiated we updated the time in CCA to the correct time - one hour ahead.
The problem: The messages being sent to our PC's when a caller leaves a voice message is 1 hour ahead of the actual time.
Please let us know if you may have a solution for this problem.
Thank you,
Dawn

Okay, I ran the update... Two problems here.
1. Now my calendar events between March 11 and March 31st 2007 are off by an hour (although they show the correct time when you open the event to view it).
It doesn't work to delete the event and create a new one... It still shows as the wrong time. the only way I found to fix the time problem is to set each event for the incorrect time zone (I'm in Pacific and have to set it to Arizona).
2. Each "all day event" I scheduled into my calendar show up the day before the actual event date, yet when I open the event they show the correct date. Example - If I scheduled an all day event for April 19th, it appears on my calendar on April 18th. Yet, when I open the event to view the details, it does say "April 19".
The only way I've found to fix the birthday events to the correct day is to delete each one and re-schedule.
I find this highly inconvenient and and huge time waster. My business depends on my calendar being accurrate and I don't have time to adjust hundreds of entries.
If other folks are having this issue, speak up. It would be great if other folks knew they should wait to install this until a fix is issued.
If it's just me... Well, I guess that *****.
What now?

TimeZone getDisplayName and Daylight Saving Time

Hi all,
Is this a good way to get "CST"/"CDT" accurately?:
// Determine whether or not we're in Daylight Saving Time
// (affects the CST/CDT/etc. printing in the output).
boolean isDst = false;
if (cal.get(Calendar.DST_OFFSET) != 0) {
isDst = true;
Thanks so much :-)

I'd use one of the TimeZone methods, for instance inDaylightTime(date); one of the other DST methods may work better for you.

Exchange Active Sync UTC Daylight Saving Time

Color me a bit confused. I am attempting to write an IOS client application to communicate with Exchange ActiveSync and display calendar information. But I am seeing some conflicting information in the protocol docs when compared to what I am getting from
Exchange. Either that or I am somehow misinterpreting one or the other.
My intent is to save an appointment in my local database in Coordinated Universal Time and then have the UI read in the information and display it as appropriate to the local timezone. In this way an recurring appointment created before daylight saving time
for Noon will still be at the same time of day in local time as an appointment created during daylight saving time for noon. But they are not.
My understanding of the documentation is as such:
In MS-ASCAL pdf section 2.2.2.40 (roughly page 34) it says for Start Time that : ...the value of this element is a dateTime data type as specified in MS-ASDTYPE section 2.3.
Moving to MS-ASDTYPE section 2.3 (roughly page 7) the dateTime value is specified in the format of ISO-8601 and all dates are given in Coordinated Universal Time (UTC)
Looking up coordinated universal time I see that UTC does not changed with the seasons as local or civil time does and therefore DOES NOT support daylight saving time. This makes sense, as DST is decidedly local and is ignored by many areas. You cannot know
from the perspective of UTC whether or not to apply a DST offset without knowing what timezone and area the time represents, therefore no daylight saving time can be supported. Based on this information I should be able to just slap the dates into my database
as they are and merely have the UI adjust itself to display them properly.
However, as a tested I began seeing a divergence of an hour between the two appointments in the database before the UI has even read them. To confirm this I created two recurring appointments representing Lunch at 12 noon local time. One that starts on March
1st 2014 (Standard Time) and one that starts on March 10th 2014 (daylight saving time) in the eastern timezone. This should be March X 2014 at 1700 hours in both cases should it not?
In the WBXML/XML that I am receiving I am getting two different times. The appointment that starts during standard time gives me a start time of 20140301T170000Z. The appointment that starts after daylight saving time is in effect locally gives me 20140301T160000Z.
The difference between the two times is 1 hour, which is the daylight saving time offset. It is my perception based on everything that I have read both in the microsoft protocol documentation and outside it that these two times should be the same and that whatever
client that gets to display them should be the one putting the offset in place as needed. Noon local time is noon local time but local time is the province of the local municipality/timezone, not that of UTC.
So my question is what exactly is going on here? Are the start/stop/date stamp date times in UTC or not. If they are in UTC, then why are they offset by an hour instead of being at the same time? Obviously outlook displays these correctly for local time,
because both appear at noon. But in my case my database contains locally adjusted times instead of the UTC times I thought I was getting which is throwing off when those appointments appear in the UI.
Can someone please clarify what's going on here and what I should be seeing?
Thanks.
E

Thanks for the reply, however after doing what is said the problem still remains. I did not try the manual approach, because of the time that would take with calendars that change at least daily.
I am running the latest update of ICal and IPod, you would think this would have been addressed with one of the updates to allow the sync to work correctly with 5th generation IPods.
I am going to try and turn off day light savings time set the clock to a Central Time zone and see if that works, I do not cross time zones much, anymore.
MacBook Mac OS X (10.4.9)

USA Residents: Early Daylight Saving Time *Changes*.

Apparently, a few folks are unaware of the changes & patch because for various reasons they do not check and/or use their Software Update Control Panel.
http://docs.info.apple.com/article.html?artnum=305056 About Daylight Saving Time changes in 2007

I have a similar issue where we cannot upgrade the jdk 1.1 without involving a lot of effort. If we keep the same old jdk, can someone tell me if use of Date and Calendar api will be impacted by the Daylight saving change.....provided the timezone is default and not explicitly set to EST. Also there isnt any timezone related buss logic.

Gmt vs. labview daylight saving time XL

I am manipulating XL sheets with time& dates. Everything works fine except that all XL times are in GMT (number of fractional days since 1900). No problem to jump to Mac 1904 reference, but a problem to get rid of the daylight saving time offset without changing my Windows setting. Is there a way to get dates and times in string readable format from my GMT number from the time of EXCEL? In other words, can I get the offset somewhere from windows to adjust the number of seconds since 1904 to eliminate this daylight offset? Not the offset of the current time, but well the offset of the past instant from my XL sheets.
I could do that via XL and activeX, but I suspect someone has a vi to do the trick.
I guess the time jumps for daylig
ht saving times lies somewhare in Windows.
Gérard

It looks to me like the "is DST" output of Seconds to Date/Time always works on today's date, not a date/time record you pass to it. So, you can use it to tell if Daylight Savings Time is active now, but you can't use it to check if DST was active at a particular date and time, without changing the system time clock in the PC.
See the attached LV 6.1 VI.
Attachments:
Is_DST.vi ‏33 KB

Daylight saving time causes a date error on 01/APR

Similar Messages

Maybe you are looking for