I have two fields, field A contains inventory types, field B contains information about a particular inventory item.

I need field B to contain a value (not empty) when Field A's content is equal to "item 1" but it can remain empty for any other inventory item that is not "item 1".

Could someone please give me some guidance? I've tried several Validation by calculation formulas but can't get it to work at all.

Any help would be appreciated.

Could you make field B a calculation field, or do you need to have the ability to enter data into it manually?

Jerry

I'm tracking inventory items, so if the item being logged is a paper roll (field A), the user must fill in the roll weight (field : and the roll weight will vary from roll to roll. So I can't use a calculation field.

Hi hcoe,

Attach this validation to Field B. While in the calculation dialog, uncheck 'Validate Only If Field Has Been Modified.' Click 'Strict' Do not allow User Override and provide a message "If FieldA is Item1 you must enter something in FieldB." Validation calculation would be:

FieldA = "Item 1" and not IsEmpty(FieldB) or FieldA <> "Item 1"

LaRetta

I hate validations, mainly because of the absurd buttons FMP uses. So ..

If it really MUST be strict, use a looping script when you give the user the new empty record and don't let it (the user) out until it has filled in both fields.

Otherwise, have a calc field, MT Msge -

Case(not IsEmpty(FieldA) and IsEmpty(FieldB), "Fill in FieldB, Dopey", "")

and put MT Msge next to FieldB, with no borders and text coloured red.

Hi LaRetta, That was exactly what I needed. Thanks!

LaRetta said:

Hi hcoe,

Attach this validation to Field B. While in the calculation dialog, uncheck 'Validate Only If Field Has Been Modified.' Click 'Strict' Do not allow User Override and provide a message "If FieldA is Item1 you must enter something in FieldB." Validation calculation would be:

FieldA = "Item 1" and not IsEmpty(FieldB) or FieldA <> "Item 1"

LaRetta

thanks for the tip, i'll try that.

Oldfogey said:

I hate validations, mainly because of the absurd buttons FMP uses. So ..

If it really MUST be strict, use a looping script when you give the user the new empty record and don't let it (the user) out until it has filled in both fields.

Otherwise, have a calc field, MT Msge -

Case(not IsEmpty(FieldA) and IsEmpty(FieldB), "Fill in FieldB, Dopey", "")

and put MT Msge next to FieldB, with no borders and text coloured red.