Our database (db/2) stores a null date as '0001-01-01'. When we upgraded to Crystal Reports 9.0 it no longer recognizes the date as '0001-01-01' it interprets it as '2001-01-01'. There are work arounds but that would mean touching hundreds of reports with possibly several dates per report that would have to be modified. We have worked with Seagate and they state that it's a limitation with the variant and they see no fix in the future.
I am just trying to find out if anyone else has experienced this problem and what, if anything, have they done about it.