MEMO NN DELETE
John Esak
john at valar.com
Wed Aug 18 06:14:30 PDT 2004
I duplicated your scenario on 5.0.13 SCO o/s 5.0.6.
and
> Then I ran the following OUTPUT process:
>
> IF: mod(@rn,"2") eq "0" 'even records numbers
> THen: MEMO Memo_Number DELETE;end
> IF:
> THEN: Memo_Number="";end 'odd record numbers
>
> Now I was told that assigning a null to the Memo field was the same as
> using MEMO NN DELETE. I will show you that that is not the case.
>
> But the results are not what you might expect.
>
> While each record did have the data in the blob erased and the memo
> could no longer be displayed, the data in the field called Memo_Number
> was not correct.
>
> All the first 6 records that had listed: MEMO************ when they
> validly had memos still displayed the MEMO************* text.
>
> The records that did not have any MEMO and displayed MEMO---------------
> are a mixed bag.
>
> All the even records still display MEMO--------------
> All the odd records display MEMO************* - indicating that a memo
> is allocated to the record.
>
> I am trying to explain to Ken that when the memo is deleted the memo
> field should reflect the missing memo by displaying MEMO------------
>
I agree with your conclusions. I think a memo field that has nothing in it
(or has been deleted... or cleared with ="") _should_ be seen (and
test-able) as MEMO------------. What is Ken's reasoning for thinking
MEMO************ is okay for an empty MEMO field???
John
More information about the Filepro-list
mailing list