Hi there Sesame pro's.

I have a small issue with a water analysis results form in am polishing up.

On the form there are several elements such as Color, Iron, Manganese, Hardness with number fields to the right of each parameter in which you enter the analysis results that all have to be between certain values in order to be marked either Good or Bad in the status text fields to the right of the number fields. I also want to clear the status field if the number field is left empty.

Example: Color has to be between 0 and 15.

/* Enter Color analysis value into R01 number field
/* Status shows up in status R011 text field

IF R01 >= 0 AND R01 <= 15
     {
     R011 = "Good"   
     }      
ELSE IF R01 > 15
     {
     R011 = "Bad"
     }      
IF R01 = ""
       {
       CLEAR(R011)      
       }

The problem with this is when we enter 0 (zero) in the number field it will not enter Good in the status field but just clears the field as if the field was empty so I gather that Sesame treats 0 (zero) and "" as identical. The problem is we often have a result of 0 in the results and status should say Good. I tried for a day to play around treating the number field as text and other functions but no luck.
Such a simple function is turning out to be a brain twister.

Hi Ray and thank you for your reply.

Sorry for my delay. Unfortunately this is not working.

The result field can have four possible entries where the status field then shows if the input is Good or Bad or Blank.

If R01 gets                                 R011 should show
1 to 15                                       Good
16 and up                                  Bad
Blank                                         Blank
0                                               Good

The problem is even if you use @Isblank or If R01 = "", both of these see the 0 entry as a Blank entry but the zero is not blank, it's 0 and needs to be seen as Good for the sake of a water analysis, like having 0 Iron is Good, not blank.

Maybe Sesame would need a new command like @Zero where it is treated like a real piece of information and not just equal to a blank condition, but there has to be millions of databases out there dealing with zero as a tangible value (Good) and where a blank entry produces a blank status (no value).

Leon

Hi Leon,

I apologize that's what I get being in a rush. Yes the issue was the >= in the first If statement. Another way to write it would be

IF @IsBlank(R01)
{
       CLEAR(R011)
}
Else IF R01 >= 0 AND R01 <= 15
{
     R011 = "Good"
}
ELSE IF R01 > 15
{
     R011 = "Bad"
} 

The reason why this is happening is because when you are comparing a numerical element value in code to a number there is no such thing as a blank number. So a blank element is 0 in terms of programming. So in the code above, you handle a blank first and then handle all actual numbers later including an actual 0.

-Ray