Re: HELP! YEAR 2000 BUG: How will it affect you?

"Jason Massey" <jmassey@ricochet.net> wrote: >The real problem I know about has to do with the day of the week. Normally, >leap year is every 4 years. However, because the earth takes 365 days 5 >hours and 46 minutes to circel the sun, adding a day every four years >overcompensates by a few minutes. To compensate for this overcorrection, >the Gregorian calendar skips leap year in centuries divisible by 400. All >the bios' written for PC's have a February 29th in the year 2000. That >throws off the date math and the day of week. The easiest way to handle this is to write a simple function that checks all 2/29/2000 dates and updates them to 3/1/2000. You can then loop through the database to change them all. Or you can add a function to the form load event which will make the change. Or you can or you can simply change the system date for all records which will default to it. To quote Microsoft "This is a non-issue" The DateDiff function is the only one which will not work correctly, and is in the process of being changed. Access 97 as well as all MS products, will use a 2 digit change through the year 2029, when presumably, there should be no further problems. On-Site Solutions Arvin Meyer e-mail: talk2am@esinet.net voice: (804) 973-9140