Or you can change your company motto to "In business since 1753"

Amusingly enough we noticed this with the cancel date on an order of Dr. Who items.

Working as designed. Customize any reports to suppress the date when it equals this value.

Hi Kevin,

I understand that is the official answer but the amount of work to do that frankly makes it a horrible answer. All of the crystal reports, custom forms, and all of the external tools (access db's/sql stored procs/3rd party integrations) need to be modified and each one could have multiple dates in them.

Even business insights (which as a SAGE tool you would expect to take the date into consideration if this were working as designed) displays the crazy dates.

How is all of that work a better answer than modifying the SQL tables to allow nulls in those fields?

Better is a matter of perspective, and please don't shoot the messenger (I don't work for Sage).
Would it be nice if Sage reprogrammed things to have blank date fields in SQL? Of course... but I'm not going to hold my breath. Users can be just told that such dates are to be treated as blank, with zero risk / zero cost. (That's what I start with... only making the edits in reports upon specific request).
If you're willing to accept the risk of changing how dates are stored by editing SQL database table settings... that is not something I would EVER recommend without extensive , exhaustive testing to ensure doing so doesn't break anything. One of the field in your original post was from an Enhancement, further complicating things, increasing risk of any changes. Any product update could introduce new bugs too with such a deviation from standard configuration, and if anything goes wrong...? No, too risky for me to even look in that direction.
If you want to be proactive, perhaps look on the ideas site to make the suggestion. With enough votes, they may consider it.

Hi Kevin,

I appreciate your responses. I might dislike the answers (don't we all just want things to go our way) but my frustration is not directed at you.

Going from a Providex version of Sage to a SQL one has been nothing short of fantastic for us on several fronts but this one piece of it has really made me shake my head in wonder. These dates were blank in the past on the old system. Rhetorically speaking, why couldn't they have left that the way it was?

I'll leave the SQL tables alone and just tell my users to ignore those dates as they appear (<snarky>...on everything</snarky>). :) Thank you again for your help.