This always reminds me of Who's on First, it makes your head spin.
But to my way of thinking and what I think would make sense to users
Hello is only = to Hello therefore <> to anything else
so with EQNULL ON or OFF the Pause statement should fire because
no matter what Hello can not be = to a blank field or a null or empty field
Hello can only be = to Hello
The same for <> Hello is = to only Hello therefore <> to everything else.
Am I nuts or just not getting this. Maybe my RBrain is set Off?
Marc
----- Original Message -----
From: [EMAIL PROTECTED]
To: RBASE-L Mailing List
Sent: Friday, April 11, 2008 8:31 AM
Subject: [RBASE-L] - Re: EQNULL ON or OFF
Marc:
For you, the danger would be to set it OFF right now without checking your
programs. If your programs were done with the assumption that eqnull was set
ON, then you better not change the setting. Here's the main difference:
set var vtext1 = 'hello', vtext2 text = null
if vtext1 <> .vtext2 then
pause 2 using 'they are not equal, so do something'
endif
if eqnull ON, then the pause would evaluate because it is able to compare a
null to a value. If you eqnull is OFF (which I believe the majority of us do),
then a null cannot be compared with anything and the pause would NOT evaluate.
Karen
Marc,
When EQNULL is on, R:BASE doesn't distinguish a null from a zero, so any
average calculations are screwy.
Bill
On Fri, Apr 11, 2008 at 8:41 PM, Marc <[EMAIL PROTECTED]> wrote:
After reading the other thread I got nervous about my EQNULL setting.
I have it set to ON, so now I am worried. I had a problem sometime back
and setting EQNULL ON fixed that problem so I just leave it on.
What are the dangers with it ON?
thanks
Marc
