December 18, 2006, 04:38 PM
MoogleThank you for the quick reply, Prarie.
I tried this out, and it seems to only affect the display of the report output. The comparison between the two fields is still failing to generate a match.
I am thinking of doing a define for both the fields that checks if they are null and sets them to a bogus value ("Null"), just to compare the two. I'll let you know how that goes.
Cheers,
Joey
December 18, 2006, 05:43 PM
susannahJoey
the NODATA symbol is as you detected just an edit mask, not anything about the content of the field.
I'm thinking that matching on two non-existent values is, philosphically, not actually possible. They each specifically dont' exist.
Could you, define two new fields
SQLEMPTY/I1=IF field1 IS MISSING THEN 0 ELSE 1;
etc
and use those dummy fields as the basis for comparison?
December 19, 2006, 08:11 AM
hammo1jIf you have a SQL and Oracle data sources wf will manage the comparison so it is possible to test null against something.
WHERE F1 EQ F2 OR F1 EQ MISSING AND F2 EQ ' ';
Should do the job if F1 is the field that appears as a dot and F2 the blank.
December 29, 2006, 10:25 AM
KerryHi all,
FYI, Joey was able to do a DEFINE that checked for IS-NOT MISSING and also for NE '', and replaced the contents with a 0 or the actual value. Both fields compare properly now.
Thanks for everyone's input. Wish you all have a happy holiday!
Cheers,
Kerry