Results 1 to 2 of 2

Thread: year crossover bug

  1. #1
    Linda Johanning Guest

    year crossover bug

    I have been told by a vendor that MS SQL Server's *determination of weeks does not cross year boundaries*--meaning for any new year--that it doesn't count the number of weeks correctly. I.e. for the year 1999 week #53 was 12/26 - 12/31 and for 2000 week #1 was 1/1 - 1/1/.

    I have searched the Microsoft site and was unable to find anything on a bug of this nature. Anybody know of any such thing or have any *ammo* that I can *shoot* at the vendor to prove this theory to the contrary?

    Thanx much ;-)
    Linda

  2. #2
    Guest

    year crossover bug (reply)



    Why not just test it yourself and see?


    ------------
    Linda Johanning at 1/4/00 12:19:58 PM

    I have been told by a vendor that MS SQL Server's *determination of weeks does not cross year boundaries*--meaning for any new year--that it doesn't count the number of weeks correctly. I.e. for the year 1999 week #53 was 12/26 - 12/31 and for 2000 week #1 was 1/1 - 1/1/.

    I have searched the Microsoft site and was unable to find anything on a bug of this nature. Anybody know of any such thing or have any *ammo* that I can *shoot* at the vendor to prove this theory to the contrary?

    Thanx much ;-)
    Linda

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •