Hi Mike Its a quick response, not thought through properly but why accept null dates in your database? Could you allow a "formatable" date like Microsoft's 1/1/80 to mean "null" . Then update your databases "once and for all" to these values. Any programs adding data would need to enforce this rule, but at least your labelling would work?
Its not answering your question I know but hopefully its a potential solution. An alternative :- You could do a select on your table to split data into valid dates and non valid dates. You could map both layers but just label valid date layer. Regards Bob MapsByDesign.co.uk <[EMAIL PROTECTED]> writes >We have databases were we record start and ending dates. I need to be able to >query records and have the dates in the label. I have found that null values >in >these date fields are troublesome. > >For example: If I use the formatdate$(abddate) to display the date in a format >that is easy to read and abddate=null; I get an error message instead of a >label. > >So I tried to make different layers-one non-null & one null. I couldn't quite >get it right, there always seemed to be records "fall through the cracks". >(there isn't a isnull() function) > >I have looked for a solution and haven't found much. At this point, I believe >that I'm going to have to query the data into different layers (if I want to >use >the formatdate$() function). > >How do I separate the null date values from non-null date values? >Can you put a conditional statement in a label expression? > >thanks. > >_______________________________________________ >MapInfo-L mailing list >[email protected] >http://www.directionsmag.com/mailman/listinfo/mapinfo-l -- bob young _______________________________________________ MapInfo-L mailing list [email protected] http://www.directionsmag.com/mailman/listinfo/mapinfo-l
