>That said, has anyone run into this? I'll probably contact MS about it to see what they say but I can't find anything on the MS KB so far.


We have a similar issue when we upgrade our customers from our 2.6a app to our SQL Server app. We wrote a 'audit' program that reports any anomolous dates. We also change common mistakes like a year of 0200 to 2000, etc.

Once the user fixes all the dates, the audit program will report no more anomolies then they can run the upgrade.

BOb