Dana,

Of course. You're correct in that DO CASE... is not what I'd need and several IF statements would be required. Anyway, if there were multiple fields that needed validating, is it recommended or common to create "large" IF statements within the validation rule?

Mike

>Mike,
>
>Unless only one CASE is ever going to be true, using DO CASE would not help you. For example, if both SomeCheckHere and AnotherCheckHere would return true, the CASE would fail you, because the first one encountered to be TRUE would fire, then the program execution would continue outside of the CASE. Because of this, you will need to make separate IF...ELSE...ENDIF statements for each field validation in this method. This way each is independent of the other and all of them will be checked.
>
>Dana
>
>>Hi Gregory.
>>
>>I guess my question now is, do I have to put every "case" into this record validation rule? I mean, if I have several fields that need some sort of validating, do I then need to build a case for each and every one of them and expand on the example you provided? Something like,
>>
>>do case
>>case SomecheckHere
>> repl field with SomeCalculatedValue
>>
>>case AnotherCheckHere
>> repl field2 with SomeOtherCalculatedValue
>>.
>>.
>>.
>>case area <> Length * Width
>> repl area with Length * Width
>>.
>>.
>>.
>>
>>endcase
>>
>>TIA
>>
>>Mike
>>
>>>Mike,
>>>
>>>Put the code in the Record Validation rule
>>>

>>>do case
>>>case area <> Length * Width
>>>  repl  area with Length * Width
>>>endcase
>>>