Null Date behaviour

Meeting place for R&R customers and clients to share tips and ideas. Post your questions, messages or problems here.
Post Reply
Chris_Ransom_(Guest)
Posts: 34
Joined: Tue Oct 10, 2017 12:44 pm

Null Date behaviour

Post by Chris_Ransom_(Guest) » Fri Jul 01, 2005 11:00 am

If I create a Calculated value from a datetime field using the TODATE() function in a report and then try to filter out records where it contains Null values it doesn^t seem to work. However if I try to filter out Null values using the original database field it does. i.e. Calculated field Date_Cancel contains TODATE(DATECNCL). If I add a filter condition to include records where Date_Cancel is not Null it still ignores them. However if I ask in to include records where DATECNCL is not Null, it then does include them. Has anyone any idea why?

kfleming
Posts: 5795
Joined: Tue Oct 10, 2017 12:44 pm

=> RE: Null Date behaviour

Post by kfleming » Fri Jul 01, 2005 4:03 pm

Even though your source is a null value, doing the todate conversion results in an empty date rather than a null date.______Kathleen__R&R Support

Chris_Ransom_(Guest)
Posts: 34
Joined: Tue Oct 10, 2017 12:44 pm

==> RE: Null Date behaviour

Post by Chris_Ransom_(Guest) » Mon Jul 11, 2005 7:47 am

Oh I see. Can you tell me then what is the correct syntax to check for an empty date field in a filter please?

kfleming
Posts: 5795
Joined: Tue Oct 10, 2017 12:44 pm

===> RE: Null Date behaviour

Post by kfleming » Sun Jul 17, 2005 8:50 pm

You would use__Date_cancel not equal to __and then just press Enter in the compared to box. This will give you a {} blank date value.____Kathleen__R&R Support

Post Reply