>Once a date has been saved to the database, there's no way to put it back to NULL (as I think I mentioned earlier, this is a conscious decision on our part that NULL means "never been entered")
>
>Why not use NULL to mean "absence of value" and use logs to determine whether this (or any other) field has been entered? If the answer is that "these things happened a long time ago and it can be made to work" that's fine and I'm not criticizing, I'm just trying to identify a plan for a VFP person considering a move to NET today.


The answer is that "these things happened a long time ago and it can be made to work" ... <g>

Seriously though, the only time that allowing the '1/1/1900' date as a default becomes a problem is when '1/1/1900' can be a valid date in a given application. This is not the case with our application and so we use it. Another date could be just as easily substituted that *wouldn't* be a date that would ever be used for your particular application.

~~Bonnie