This one looks like a bug in D3...

When I use the DateTimePicker in a form, and then try to assign the
chosen value to a text box, along the lines of:

textbox.text:=datetostr(datetimepicker.date);

I get a message telling me, for example, "18-Jun-1999 is not a valid
date". This is when my Windows settings are to show short dates as dd-
mmm-yyyy format. If I set it to dd-mm-yyyy, then Delphi happily accepts
"18-06-1999" as being a valid date.

Does anyone know how I can best get around this one? If I ship my app I
don't know what wacky permutations it might encounter!

TIA

-jhn
--
Return address removed for anti-spam purposes.
Email replies to news at maelstrom dot demon dot co dot uk
Email replies to this address may be copied to relevant newsgroups

TDateTimePicker is a dog of a component (with fleas)
(Try putting a year of 2001-2009  into it.)
I tired of trying to work around its bugs and bought the Adrock Datetime
suite for about $50
It works perfectly and has paid for itself in saved time.

Cheers,
Craig

In article <GXPcoJA58qb3E...@maelstrom.demon.co.uk>,
  Black Hole <Black.H...@Black.Hole> wrote:

[snip]

actually I think you will find that the TDateTimePicker is a wrapper
around the microsoft control, so any problems with the control are
probably more likely from MS.  BTW, try changing the colour of the text
in the control.  This "bug" has been in the control since D2 and it is
still there in D4.

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

In article <7kp0pe$lc...@nnrp1.deja.com>, th...@my-deja.com writes

Sorry, I'm not quite with you - are you saying that changing it to blue
on white instead of black on white may help the issue?

As for it being a MS bug rather than a Delphi bug, it's a concept I find
entirely believable...

-jhn

--
Return address removed for anti-spam purposes.
Email replies to news at maelstrom dot demon dot co dot uk
Email replies to this address may be copied to relevant newsgroups

In article <YrkbXXAJlWc3E...@maelstrom.demon.co.uk>,
  Black Hole <Black.H...@Black.Hole> wrote:

No, but just that if your problem IS a bug, I would not hold my breath
waiting for Microsoft to fix it, you could be a very old man by then!

trevor

and unfortunately that means that it doesn't appear that it will be
fixed soon, certainly not in this millenium.....

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.