Hi!

From what I know, empty date is in VFP only. ODBC and OLE DB works for MANY data sources, that cannot work with empty dates. So ODBC and OLEDB work with the range of date values that is acceptable for ALL data sources they can handle. Do you understand this point? What if you store data on SQL Server? It have no emty date. That is why it is recommended to do not use the empty date value and use NULL value instead. Empty date value comes from the older FoxPro versions and I wondered why MS did not suggested to make note in all help files to do not use it because it is obsolete.



>>Hi!
>>
>>It is better to use NULL value for a date field instead of emoty date, so you require only to specifu NullDisplay option.
>>
>>Well, I see for a first time that LOCAL view cause this converting. Are you sure that local view is not built on the remote view?
>What do you mean?
>
>>As far as I know, such convertion done by ODBC used to get data by remote view.
>
>Isn't it that Local View and Remote View may have the same definition but uses different methodology to access data? The first one is native but the other one uses ODBC or OLE DB. We use Remote instead of Local to make it compatible with SQL Server at least.
>
>But why the need to have 12/30/1899 in an empty date field? MS Team should fix this...