Hi Erik,

I was just curious as to why you think that empty date is a strange concept. In real life I come across lots of forms where I leave a date blank, simply because it doesn't apply (to me) or because I think it's none of their business.

I find the reverse to you - that it is strange when a feature/facility does not support an 'empty date' field.

I guess this is also similar to now having the NULL capability. Before, I gues that programmers doing medical stuff had to tell their users to interpret zeroes in a particular way in the BLOOD PRESSURE field. Having NULLS takes care of this now.

Cheers,

Jim N

>>Hi
>>I'm using ADO from an ASP page to query a FoxPro table using the VFP ODBC driver. One of the fields in the query is a date field - 'date_deliv'. When this field is empty in the Fox table, the ADO recordset contains "12:00:00 AM". Apparently ADO is treating the field as a DateTime field. I checked the ADO data type for the field, and it is a dbf date type field. Is there any way to have ADO return empty date fields without inserting the time, or do I have to check the field for a value of "12:00:00 AM" to determine if I have an empty date?
>>
>>TIA
>>Bill Sabo
>
>I don't think the OLEDB provider for ODBC sources has a concept of empty dates. (It's a pretty strange concept if you think about it). I think you're in for some manual work.