Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!weretis.net!feeder4.news.weretis.net!feeder.news-service.com!aioe.org!.POSTED!not-for-mail From: "Nobody" Newsgroups: comp.lang.basic.visual.misc Subject: Re: Possible Date Bug Date: Sat, 16 Jul 2011 03:48:46 -0400 Organization: Aioe.org NNTP Server Lines: 25 Message-ID: References: NNTP-Posting-Host: 2zkn8lvDl69X1tm9Wtth7A.user.speranza.aioe.org X-Complaints-To: abuse@aioe.org X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-RFC2646: Format=Flowed; Original X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: Microsoft Outlook Express 6.00.2900.3028 X-Priority: 3 X-MSMail-Priority: Normal Xref: x330-a1.tempe.blueboxinc.net comp.lang.basic.visual.misc:351 "Dr J R Stockton" wrote in message news:hcJhIUE03KIOFwHE@invalid.uk.co.demon.merlyn.invalid... > In 2003, as you may recall, December 29th was a Monday. The nearest > Thursday was January 1st 2004, and the ISO 8601 week number was > therefore 1, written "01". > > Perhaps you are not familiar with ISO 8601? > > There are errors for 2003-12-29, 2007-12-31, and 2019-12-30, in > IE4, IE6, IE7 & IE8 - intervals 4, 12, 12 years recurring, > except across missing Leap Years (I did not test IE5). There is a > different error for 2101-01-02, +/- any multiple of 400 years. > > You did not say what version of VB gave what result. You are right. Searching for "DatePart bug" in MSKB shows this article: BUG: Format or DatePart Functions Can Return Wrong Week Number for Last Monday in Year http://support.microsoft.com/kb/200299 VB6+SP5 on XP Pro+SP2 returns 53 for the code line that you posted in the OP.