I've only just at this previous thread
(http://www.google.ie/groups?safe=images&ie=UTF-8&as_umsgid=10d5001c26af9%24
66cb84d0%2439ef2ecf@TKMSFTNGXA08&lr=&hl=en)
However, it seems that is doesn't need any solution from MS to rectify the
problem. IMHO, it's the fault of Marco's program in mixing 2 different date
locales (i.e. the implicit system/user one) and the explicit picture string.
Once the code is changed appropriately then it works OK.
To illustrate the problem a little more, I have a default date format of
dd/mm/yyyy on my machine (i.e. UK format). If my explicit picture string is
mm/dd/yyyy (i.e US format), then I get exactly the same symptoms as Marco.
Private Sub Command1_Click()
Text1.Text = Format(Text1.Text, "mm/dd/yyyy")
End Sub
Basically, Text1 is being used to display an explicit US-format date, but
the call to Format() assumes it to be a UK-format date. It can't be both!
Tony Proctor
> (In reference to 2002 thread "VB Date")
>
[quoted text clipped - 7 lines]
> Cheers
> Hilton