Thanks for the clarification ...

>>Cetin/Pete/Cindy
>>
>>I have been following your thread(s) concerning blank or empty date fields in VFP comming over to .NET as '12/30/1899' or some other old date. I am currently writing a Web Form application that uses VFP tables (v7.0) and allows the user to enter some dates and then save them back to VFP via the VFP9.0 OleDb data driver. I am seeing the same thing as Pete, the blank or empty date fields come over as '12/30/1899'. Once my user replaces the date, then the system brings back the new date just fine. When I look into the VFP table where the date fields are, they are still empty.
>>
>>I have two questions:
>>1. Is this because of the VFP9.0 OleDB driver or an incorrect display format setting in my web form control?
>>2. If this is because of the OleDb driver, How can I display empty dates on my web form ?
>>
>>Thanks for any assistance you can provide.
>
>1) No there is nothing wrong with the driver. VFP data can have 'empty' dates where other backends define it as a datetime + do not accept an empty value. It's an 8 bytes value composed of 2 integer parts, one holding the date from a base date (and thus 0=12/30/1899), and other time part.
>
>2) It's not. If you allow date/dateime to accept null and use null instead of empty values then you could control with System.DBNull
>
>Cetin