Re: datediff bug between vb6/vbscript and vb.net
- From: "Bill" <Bill@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 21 Apr 2005 10:11:02 -0700
To show I am a dinosaur I could take a ibm cobol 360 program written at the
dawn of time and with just a few very simple changes for todays new os
environment EVERTHING would work EXACTLY the same. This vb stuff is poop.
Thanks for your quick reply...maybe if I convert to the dates to seconds and
do the math myself I can continue. Then change my datediff stmts everywhere
in my application.....Oh the pain, the pain. Thanks Again !
"Bob Butler" wrote:
> "Bill" <Bill@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:B40B42A9-
> 5E30-4412-BB82-378CFF4EB88B@xxxxxxxxxxxxx
> > What is going on ?
>
> This was one of the things that really drove me nuts when I was looking at
> the early versions of VB.Net.... When you ask for 'days' using DateDiff in
> VB it ignores the time portion so the difference between 11:59PM one day and
> 12:01 the next day was 1 day. In VB.Net the DateDiff function (from the
> *compatibility* library no less) returned the number of whole days so it
> gave the difference as 0 days. This, of course, meant that when the
> "upgrade wizard" (yeah, right...) converted the code it actually produced
> stuff that did not act the same way. It was yet another indication that
> porting from VB to VB.Net meant examining, probably revising, and definitely
> testing every single line of code. VB6 is end of the line for VB code.
> VB.Net is *not* the same language and any surface similarity is there only
> to try to confuse and mislead people into thinking that MS still supports
> VB.
>
> That said...
>
> --
> <response type="generic" language="VB.Net">
> This newsgroup is for users of Visual Basic version 6.0
> and earlier and not the misleadingly named VB.Net
> or VB 200x. Solutions, and often even the questions,
> for one platform will be meaningless in the other.
> When VB.Net was released Microsoft created new newsgroups
> devoted to the new platform so that neither group of
> developers need wade through the clutter of unrelated
> topics. Look for newsgroups with the words "dotnet" or
> "vsnet" in their name. For the msnews.microsoft.com news
> server try these:
>
> microsoft.public.dotnet.general
> microsoft.public.dotnet.languages.vb
>
> </response>
>
>
.
- Follow-Ups:
- Re: datediff bug between vb6/vbscript and vb.net
- From: Norman Diamond
- Re: datediff bug between vb6/vbscript and vb.net
- From: Bob Butler
- Re: datediff bug between vb6/vbscript and vb.net
- References:
- datediff bug between vb6/vbscript and vb.net
- From: Bill
- Re: datediff bug between vb6/vbscript and vb.net
- From: Bob Butler
- datediff bug between vb6/vbscript and vb.net
- Prev by Date: Re: datediff bug between vb6/vbscript and vb.net
- Next by Date: Re: datediff bug between vb6/vbscript and vb.net
- Previous by thread: Re: datediff bug between vb6/vbscript and vb.net
- Next by thread: Re: datediff bug between vb6/vbscript and vb.net
- Index(es):
Relevant Pages
|