Hi All,

I did not have a chance (changed a lot of interfaces) to upgrade to 2.05
or 2.06 and still using 2.04 latest, and until now I have used
webcals.wbs from i think it was from 2.05 to fix errors with dates
showing errors, but today my dates are saved on database with wrong date
(28.oct instead of 29.oct).. It might be related to change to winter
time somehow, but I am not sure.

I cannot use 2.06 webcals.wbs, it simply fails opening the ide. And I
know it's not the correct way, but it was a workaround until now.

Has anyone the same problem or what can be done - besides upgrading to
latest 2.06 which probably does not have the problem?

Thanks in advance,

Hüseyin

Update:

It seems that the problem does not occur today as 30.oct.

Regards,

Hüseyin


Den 29-10-2017 kl. 17:20 skrev Hüseyin Aliz:
> Hi All,
>
> I did not have a chance (changed a lot of interfaces) to upgrade to
> 2.05 or 2.06 and still using 2.04 latest, and until now I have used
> webcals.wbs from i think it was from 2.05 to fix errors with dates
> showing errors, but today my dates are saved on database with wrong
> date (28.oct instead of 29.oct).. It might be related to change to
> winter time somehow, but I am not sure.
>
> I cannot use 2.06 webcals.wbs, it simply fails opening the ide. And I
> know it's not the correct way, but it was a workaround until now.
>
> Has anyone the same problem or what can be done - besides upgrading to
> latest 2.06 which probably does not have the problem?
>
> Thanks in advance,
>
> Hüseyin
>
>

Huseyin,

<< I did not have a chance (changed a lot of interfaces) to upgrade to 2.05 or 2.06 and still using 2.04 latest, and until now I have used webcals.wbs from i think it was from 2.05 to fix errors with dates showing errors, but today my dates are saved on database with wrong date (28.oct instead of 29.oct).. It might be related to change to winter time somehow, but I am not sure. >>

Daylight savings time doesn't kick in until November 5th, so it's not that.  The problem is most likely related to date/time localization, but the WebCals unit won't have any bearing on any of that, so unless the date is wrong *when selected in the control*, you can leave that out of the equation.

Check to see if you have date/time localization enabled in the TDataSet in your application, as well as whether you have it enabled for the dataset in the DataSet Manager in the IDE/web server.

Tim Young
Elevate Software
www.elevatesoft.com

> Daylight savings time doesn't kick in until November 5th, so it's not that.  

The UK changed last weekend so maybe other places too.

--
Matthew Jones

>> Daylight savings time doesn't kick in until November 5th, so it's not that.  

>The UK changed last weekend so maybe other places too.

Australia changed on 1st of October.

In Denmark the change was yesterday (29.oct).


Den 30-10-2017 kl. 21:30 skrev Matthew Jones:
>> Daylight savings time doesn't kick in until November 5th, so it's not that.
> The UK changed last weekend so maybe other places too.
>

Tim,

In Denmark we ended daylight saving time this weekend (29.oct).

If it's "LocalizeDateTimeColumns", than yes it's enabled both in the app
and also in ewb webserver. It was both with calendar control (selecting
date) and saving the dataset with .asDate := Date without a control that
the problem was existing.

Regards,

Hüseyin


Den 30-10-2017 kl. 20:17 skrev Tim Young [Elevate Software]:
> Huseyin,
>
> << I did not have a chance (changed a lot of interfaces) to upgrade to 2.05 or 2.06 and still using 2.04 latest, and until now I have used webcals.wbs from i think it was from 2.05 to fix errors with dates showing errors, but today my dates are saved on database with wrong date (28.oct instead of 29.oct).. It might be related to change to winter time somehow, but I am not sure. >>
>
> Daylight savings time doesn't kick in until November 5th, so it's not that.  The problem is most likely related to date/time localization, but the WebCals unit won't have any bearing on any of that, so unless the date is wrong *when selected in the control*, you can leave that out of the equation.
>
> Check to see if you have date/time localization enabled in the TDataSet in your application, as well as whether you have it enabled for the dataset in the DataSet Manager in the IDE/web server.
>
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Hüseyin Aliz wrote:

> saved on database with wrong date

Dates, and times too, are one of the most complicated problems programmers have to face. Me, I hate them. But the first step is to work out what sort of time you are talking about. What is important to you?

The key is that there are at least three different types of times. There is an absolute time, where one time defines the moment that something happens in the world. There is a local event time, where you can describe the time that the television news will start (10pm). And you have mixes where daylight saving is mixed in. The worst ones are things like horse races, where the 3 O'clock at Sandown will run at 1400 UTC but you are in some foreign part so it is at 7pm, except you are in daylight saving to make that 8pm. And of course the person entering it just wants to say "3pm on the 19th July next year" and not think about the DST offset. The first step is to know what you are dealing with. Then what needs to go into the database. And then you can work out what makes sense in the edit/display. It also helps to specify this so others can help better.

--

Matthew Jones

Matthew,

<< The UK changed last weekend so maybe other places too.  >>

Duh, yeah, I forgot that we all don't kick in at the same time...

Tim Young
Elevate Software
www.elevatesoft.com

Huseyin,

<< If it's "LocalizeDateTimeColumns", than yes it's enabled both in the app and also in ewb webserver. It was both with calendar control (selecting date) and saving the dataset with .asDate := Date without a control that
the problem was existing. >>

Please send me an example of what you're seeing, and I'll take a look.

Tim Young
Elevate Software
www.elevatesoft.com