Re: CDate() different value in VB6 and SQL 2005
- From: "Jeff Johnson" <i.get@xxxxxxxxxxx>
- Date: Tue, 19 Feb 2008 13:50:54 -0500
"Mike Williams" <mikea@xxxxxxxxxxxxxxxxx> wrote in message
news:O4qWFrucIHA.1168@xxxxxxxxxxxxxxxxxxxxxxx
Does anyone else experience this: CDate(34940) returns 2/15/2008 in VB 6
and the same conversion in SQL
2005 returns 2/17/2008?
Well that's weird? I didn't know there were 17 months in a year ;-)
So tell me, in England, when you speak the date, do you actually say (on a
REGULAR basis) "Today is nineteenth February, two thousand eight"?
Or "Today is the nineteenth of February, two thousand eight"?
Or do you say it like virtually everyone in America: "Today is February
nineteenth, two thousand eight"?
Because if you say it like the last one, why don't you WRITE it like the
last one? I've always wondered.
I can understand why they write it dd.mm.yyyy in Germany, for example,
because they actually DO say the day number before the month. So again, just
curious.
.
- Follow-Ups:
- Re: CDate() different value in VB6 and SQL 2005
- From: Nigel Bufton
- Re: CDate() different value in VB6 and SQL 2005
- From: Jan Hyde (VB MVP)
- Re: CDate() different value in VB6 and SQL 2005
- From: Mike Williams
- Re: CDate() different value in VB6 and SQL 2005
- From: Robert Morley
- Re: CDate() different value in VB6 and SQL 2005
- References:
- CDate() different value in VB6 and SQL 2005
- From: PrefersGolfing
- Re: CDate() different value in VB6 and SQL 2005
- From: Mike Williams
- CDate() different value in VB6 and SQL 2005
- Prev by Date: MS Software Giveaway
- Next by Date: Re: Search as you type function?
- Previous by thread: Re: CDate() different value in VB6 and SQL 2005
- Next by thread: Re: CDate() different value in VB6 and SQL 2005
- Index(es):
Relevant Pages
|