[AccessD] '6a' or '6p' Are Valid Dates?

On 20 Jun 2006 at 21:35, Dan Waters wrote:

> I was testing a new module and quickly typed '6a' into a date field,
> expecting to get an error, but no, the table thinks it's a real date! 
> Turns out this will enter 6:00:00 AM 12/30/1899.  Of course my
> customers need this 'quick entry feature'!  
> 
> 
> 
> How can I code to trap this in my form and null the field?  
> 

In the before_update:

dteEarliestPossibelDate = "1/1/1900" 'or whatever
...
If datevalue(txtSomeDate) < dteEarliestPossibleDate then
    txtSomeDate = Null
End if