Re: Format Bug When Date is > '1/1/2007'?
- From: "Tony Proctor" <tony_proctor@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 4 Jan 2007 10:24:16 -0000
Can you show us some real VB Steve. The Format() call you describe is not
proper VB and so we can't see what you're trying to do
if Format() is called with a plain text argument, and no parameters, then
I'm not sure what you are expecting. I believe VB is trying to guess whether
the text is a valid date or just some other text, e.g.
Format("2006-3-2")
is interpreting the string as a yyyy-mm-dd type of date, whereas with
Format("2006-3-92")
it decides it's not a date at all.
What would you expect your call to generate?
Tony Proctor
<stevekgoodwin@xxxxxxxxx> wrote in message
news:1167877736.679515.51030@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Has anyone encountered the Format( aString ) function behaving
differently asof 1/1/2007? I'm seeing this:
Format('070102-1') results in '1/01/4566'
and
Format('061227-1') results in '061227-1'
(as you can tell I don't usually delve into VB). This is stuffing up
one of the feeds we've got that have been working since 2003.
Anyone got any information on this? (The solution is easy, remove the
Format() function, but I'm curious as to what the cause is).
.
- References:
- Format Bug When Date is > '1/1/2007'?
- From: stevekgoodwin
- Format Bug When Date is > '1/1/2007'?
- Prev by Date: Format Bug When Date is > '1/1/2007'?
- Next by Date: Error: 7 Out of Memory
- Previous by thread: Format Bug When Date is > '1/1/2007'?
- Next by thread: Error: 7 Out of Memory
- Index(es):
Relevant Pages
|
