On investigation of a bug in a re****t, it turns out that some
work might not have any disbursements. Because I have been using
inner joins to add columns to build up the re****t data, that work does
not show up on the re****t.
I have solved this, I think, but it is not nice. Where I join
the various columns together and there is danger of .null., I have
made the joins left outer, the resulting cursor readwrite, and follow
by replaces like
replace thing with 0 for isnull(thing)
for each potentially-.null. column.
You think this is a kludge, right? So do I. It is too easy to
miss a case, and it is ugly.
Is there a better way of handling these idiot .null.s?
(I am quite aware that the sum of zero numbers is 0. A pity SQL
does not understand.)
(Yes, I could use set enginebehavior, but that is likely to bite
if I have to have a VFP 9 SQL feature.)
Sincerely,
Gene Wirchenko
Computerese Irregular Verb Conjugation:
I have preferences.
You have biases.
He/She has prejudices.
|
