Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread TDateEditComboBox and persistent load error invalid date
Thu, Apr 13 2017 9:13 AMPermanent Link

Ronald

Hi,

I know date and times are a real headache, and I am having problems again with the Date "family".
When I have an empty app with only a TDateEditComboBox on the initialization here below, I get the error:

Persistent load error(Persistent load error(Invalid date(4/11/2017)))

In the attachment you can see the result in my browser. In the TDateEditComboBox the date ends up being correctly formatted (here in the Netherlands we use d-M-yyyy). But still I get the error.

initialization
with FormatSettings do
  begin                       
  DateSeparator:='-';
  ShortDateFormat:='d-M-yyyy';
  end;

Greetings,
Ronald



Attachments: error.pdf
Thu, Apr 13 2017 11:21 AMPermanent Link

Uli Becker

Ronald,

> I know date and times are a real headache, and I am having problems again with the Date "family".
> When I have an empty app with only a TDateEditComboBox on the initialization here below, I get the error:

I guess you are still using 2.05. There was a long discussion in the
2.06 beta newsgroup with this summary by Tim:

<<
Here are the facts:

1) This issue was reported and fixed as part of 2.06:

http://www.elevatesoft.com/incident?action=viewrep&category=ewb&release=2.05&incident=4443

2) The fix had the *side effect* of causing the issue reported in this
thread, but only with developers that have somehow inadvertently pulled
in different format settings into the component library.  In other
words, the *cause* of the issue isn't the fix or any changes in 2.06,
rather the cause is a combination of mismatched format settings between
design-time and run-time usage, combined with the fact that these
controls save the textual representations of their selected date as part
of their published properties.  I've now changed it so that they no
longer have published Text properties, and the problem is solved.
>>

So in 2.06 you can let the text property empty and avoid the error.

Uli
Thu, Apr 13 2017 12:11 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Uli,

Just to clarify for those getting confused by my quoted reply:

<< I've now changed it so that they no longer have published Text properties, and the problem is solved. >>

This isn't what I ended up doing, and what you said is correct:

"So in 2.06 you can let the text property empty and avoid the error."

The Text properties are still published, but can be made blank at design-time, for the TDateEditComboBox and TCalendar controls.  This resolves that issue at design-time.

Tim Young
Elevate Software
www.elevatesoft.com
Thu, Apr 13 2017 4:47 PMPermanent Link

Ronald

Tim Young [Elevate Software] wrote:

<The Text properties are still published, but can be made blank at design-time, for the TDateEditComboBox and TCalendar controls.  This resolves that issue at design-time.>

Thanks Uli and Tim, it works fine now. Sorry that I overlooked the issue.

Still enjoying EWB (2.06) every day....

Greetings,
Ronald  
Image