Well, you can use a text field to store date values, but this poses
additional problems, see some of the other posts in this thread.
But what I'm interested in is why you think it's important that you be able
to *store* NA in the field. Would it be sufficient to leave the value NULL
(which a date field allows) and simply *display* the field value as NA in a
forum, query, or report.
For instance, in a Query, you can set the Format property to
mm/dd/yyyy;;"NA"
and if there is a date in the field it will display and if there is not, it
will display NA.
Or you could define a field in your query or report as Bdate:
nz([birthdate],"NA"), which will also display the date if there is one and
NA if there is not.
Just an alternative to think about.
--
--Roger Carlson
MS Access MVP
Access Database Samples:
www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L