Dennis,
I have not "checked" this out, but since you are looking at using EEP's
in your form, a possible solution is to simply put "Set Zero Off" as the first
line in your EEP and then Set Zero ON before your RETURN.
I believe this setting is "session specific". I.E. no other users working on
the database would be affected when this setting was toggled on or off.
(I did check out this and the setting is session specific)
-- Test.EEP
-- Check for null and then do what ever
-- Used in form XYZ
Set Zero Off
IF VTest ISNULL THEN
DO WHATEVER
ELSE
DO SOMETHING ELSE
ENDIF
Set Zero ON
RETURN
-----Original Message-----
From: Dennis McGrath [SMTP:[EMAIL PROTECTED]
Sent: Wednesday, October 08, 2003 9:32 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Problems with ZERO ON - Razzak's Reply
Larry,
The real nasty here is the inconsistency.
With ZERO ON, if I say
SELECT Colname into vTest FROM TableName where Colname is null and
limit = 1
I retrieve a NULL
If, in the form, I say
vTest = Colname IN TableName where Colname is null and limit = 1
I will also retrieve NULL
But if I say
vTest = Colname
I get zero regardless of whether the form is in enter or edit mode.
That is what needs to be fixed if anything is going to work. I wonder
if I have an ice cube's chance in boiling water to see this fixed.
then in the eep i could use:
if vTest is null then
-- whatever if null
else
-- whatever if not null
endif
Thanks
Dennis McGrath
