Hi Set

Thanks for responding.

At 11:43 pm 07/09/2004, you wrote:

>I suppose you could have two fields, one string and one date. The
>users see the string field, whereas the date field is populated
>through a trigger if the string is not empty (then the update will
>fail if the string field is not a proper date). Though this may give
>you surprises when it comes to searching and I wouldn't be surprised
>if it gave you more trouble than handling NULL in a proper way.
>
>The problem is that a date is stored as a number of days since a
>certain date, and an empty string is a lousy number.

Wow.

Actually what happens is when a date is optional like: Please enter you
birth date (optional)? People may not want to reveal the date and would
like to keep it empty. Now filling this to a date however obscure like
01/01/1245 will have problem when you would like to know about filled birth
dates.

Hasn't anybody come across situations like above, if so please let me know
how they have handles it in the past.



Regards
Bhavbhuti
___________________________________________
Softwares for Indian Businesses at:
http://venussoftop.tripod.com
namitbn@...
___________________________________________

----------


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.754 / Virus Database: 504 - Release Date: 06/09/2004


[Non-text portions of this message have been removed]