Hi.

I see your comments about using isnull for standard datatypes and isvalid for objects. And I agree. But I will mention that code like the following can be found in PFC's:

// Validate the dwo reference.
IF IsNull(adwo_obj) OR NOT IsValid(adwo_obj) THEN	 
	Return -1
END IF 

In that case, is it wrong to run both checks? Should this change to:

// Validate the dwo reference.
IF NOT IsValid(adwo_obj) THEN	 
	Return -1
END IF 

It's just a question. I'm interested if the original code needs to be fixed!

Thanks.

Andreas.

Hi Olan,

I'm not sure I understand your exact problem. You say this doesn't work as expected:

IF (isnull(adw_object)) then RETURN

While this does:

lb_valid = IsNull (adw_object)
IF (NOT (lb_valid)) THEN RETURN                    // <--- the lb_valid value is FALSE at this point, as it should be.

Yet your "This works" snippets is doing the exact opposite of what the original code did. #1 will return if adw_object is null, #2 will return if adw_object is *not* null.

Hi Olan;

   If this is reproducible, please create a support ticket.

However, the developer should have used the IsValid() command instead in the first place.

Regards ... Chris