Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 3 of 3 total
Thread Local Time Is Invalid (Situated Within The Missing Period Prior To DST)?
Mon, May 14 2018 3:36 AMPermanent Link

Frederick Chin

After updating EWB to 2.06b12, loading one of my DBISAM tables causes EWB to display the following error:-

Database load response error (The given "30/12/1899" local time is invalid (situated within the missing period prior to DST)

What is this error about? The table has tons of date fields and one timestamp field. Most of the date fields are blank and the timestamp field is filled.

There is no AfterLoad event.

--
Frederick
Fri, May 18 2018 2:16 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Frederick,

<< After updating EWB to 2.06b12, loading one of my DBISAM tables causes EWB to display the following error:-

Database load response error (The given "30/12/1899" local time is invalid (situated within the missing period prior to DST) >>

Please send me the table and I'll take a look.  It's probably an invalid date that needs to be ignored, but I'll have to see what I can do in terms of ignoring them.

Tim Young
Elevate Software
www.elevatesoft.com
Sat, May 19 2018 11:34 AMPermanent Link

Frederick Chin

Tim,

/*
Please send me the table and I'll take a look.  It's probably an invalid date that needs to be ignored, but I'll have to see what I can do in terms of ignoring them.
*/

I have found the problem. Two of the date fields has "30/12/1899" within them. If I blank out the fields, the error goes away.

Interestingly, if I enter "31/12/1899" or "01/01/1900", there is no error message.

If you can, I would prefer EWB b12 and later to work like b11 and earlier where it doesn't choke on the date because it is still a valid date.

Note: I am using the dd/mm/yyyy format.

--
Frederick
Image