You need to either store NULL values to represent "blank dates" or assume that 1/1/1900 is a blank date in your code. Either way you'll find quirks.

One one side, NULLs have a funny (yet rational) behavior, for example ( NULL > 1 ) returns NULL instead of .F. and stuff like that. Thus your date expressions (including queries) will need to address the presence of NULL values on dates directly.

One the other side, it is somewho patchy to think of 1/1/1900 as a blank date, yet this is what I do most of the times since I don't like NULLs.

>I am using SQL 2000 on the backend. When I delete a date in a remote view, issue a tableupdate and then requery the view, the value in the field comes back as 1/1/1900? Is there an easy way to eliminate this throughout a system or do I need code for every date field throughout the system to handle "empty" date fields from SQL??
>
>Thanks,
>Doug