FIeld Rules and xBasic

[OOsorio]

Let me provide an example. I have a table with 3 fieds, Field1, Field2 and Field3.
I enter data in Field1. The data entered is either AAA, BBB, or CCC.
If data in Field1 is AAA then I want Field2 to equal 111. If data in Field1 is BBB then I want Field2 to equal 222.

How can I do this in a field rule? Would this be the best place to do this or is there another option?

Thank you,

[Stan Mathews]

RE: FIeld Rules and xBasic

Ii sounds as if you want a calculated value in Field2 so I would make it a calculated field rather than user entered or auto-increment.

A calculated field rule can only consist of one expression, however complicated that may be. A nested if() expression or a case() expression may suffice. If you need more options than those provide you can create a user defined function which would be called by the field rule expression.

[OOsorio]

RE: FIeld Rules and xBasic

Thank you Stan. Can you give me an example of the code required in the fied rule for a nested if or case.

[CALocklin]

RE: FIeld Rules and xBasic

If you want to put one expression in the field rule rather than calling your own user defined function (UDF), use either the IF() function or the CASE() function. However, I highly recommend the CASE() function if you are going to nest them.

Both functions are fully explained in the Help file. Just remember to look for the function rather than the IF...THEN...ELSE or the SELECT...CASE choices.

By the way, UDFs work in a pinch but they can slow things down quite a bit. I highly recommend doing it with a single field rule expression whenever possible. It can make a big difference in "computer time". Even if the user doesn't notice the one delay, I prefer to keep things efficient because you never know what other time consuming feature(s) might get added later.

Cal Locklin
www.aimsdc.net

[Stan Mathews]

RE: FIeld Rules and xBasic

Cal's answer should get you going.

Specifically

"If data in Field1 is AAA then I want Field2 to equal 111. If data in Field1 is BBB then I want Field2 to equal 222."

if(field1="AAA",111,If(field1="BBB",222,???))

where ??? it the value to put in field2 if field1 is neither AAA or BBB.

or

case(field1 = "AAA",111,field1 = "BBB",222,.T.,???)

where ??? it the value to put in field2 if field1 is neither AAA or BBB.

[OOsorio]

RE: FIeld Rules and xBasic

Hi,
Here is the contents of the Field Rule:
'Date Created: 05-Aug-2005 05:17:00 PM
'Last Updated: 08-Aug-2005 04:29:00 PM
'Created By : oscar
'Updated By : oscar
FUNCTION Origin_Zip as C
if(ORIGIN_NAME="KRYSTAL",33178,If(ORIGIN_NAME="ST JOHN",33316,If(ORIGIN_NAME="OCEAN TERMINAL",31402)))
END IF
END FUNCTION

While using the form and arriving at field ORIGIN_ZIP, I get an error: Missing or invalid key word.

Would appreciate your help.......

[Stan Mathews]

RE: FIeld Rules and xBasic

You have a combination of efforts here. A simple nested if will suffice if this is the total of values you need to check.

if(ORIGIN_NAME="KRYSTAL","33178",If(ORIGIN_NAME="ST JOHN","33316",If(ORIGIN_NAME="OCEAN TERMINAL","31402","some value must go here")))

"some value must go here" represents the value that is returned if all the if()'s fall through to a final false value.


If your post is the beginnings of a longer function, you have to assign the return value to the function name like

FUNCTION Origin_Zip as C (origin_name AS C)
origin_zip = if(ORIGIN_NAME="KRYSTAL","33178",If(ORIGIN_NAME="ST JOHN","33316",If(ORIGIN_NAME="OCEAN TERMINAL","31402{","some value must go here")))
END IF
END FUNCTION

and the usage in the field rule would be

origin_zip(origin_name)

[Stan Mathews]

RE: FIeld Rules and xBasic

Here's an example of both, attached.

[OOsorio]

RE: FIeld Rules and xBasic

Thank you Stan.
Thank you Cal.

At last I understand.

[OOsorio]

RE: FIeld Rules and xBasic

One more question.
If the ORIGIN_NAME is not any of those three in the IF statement, then the user can manually enter the zip code.

Thanks,

[Stan Mathews]

RE: FIeld Rules and xBasic

Nope, a calculated field is a calculated field, not user entered.

Take a look at field rules, data entry, conditional default expression if you want the user to be able to enter values.