CASE funtion update

[Mike Konoff]

Hello,

The first field on my Mailings form is CODE and the second is FIRSTNAME.

In the field rules, FIRSTNAME is set as user-entered with a simple default expression; a CASE funtion. Type "1" in CODE and FIRSTNAME's contents becomes "Operations Manager", etc. I've checked "set value at start of data entry". Everything works great on initial data entry if the correct choice is made.

However, if I go back and change the value in CODE nothing happens in FIRSTNAME; the first value remains.

If possible, I would like to set this up so that when a value in CODE is changed and the field is exited, the updated value in FIRSTNAME happens automatically and immediately.

Any ideas?

Thanks,
Mike

[Bill Warner]

RE: CASE funtion update

Mike, since you have defined it as a default value, it won't change when you change the value. Default values will only appear when entering a new record. To get the value to change when changing a record, you will have to do something else.

One way is to make the field a calc value rather than default. This will allow you to make changes in CODE, and you will see the new value in FIRSTNAME.

One possible drawback is that, unlike a default field, you CANNOT edit the calc field directly. In other words, with a default field, you could put a new value in FIRSTNAME that didn't obey the expression, but you can't do this with a calc field.

If you want the flexibility of a default field, but still want FIRSTNAME to change when you change CODE, you could write a script attached to the ONSAVE event of CODE so FIRSTNAME would change.

[Stephen Williams]

RE: CASE funtion update

Yes - instead of a default it seems you want a calculated value. It will always be "Operations Manager" when the code is "1". You could also create a seperate table of Codes and Names, with the Title field rule being
lookupc("C",code,"Title","Names_n_Codes.dbf","Code")
or lookupn(...) if the code is a number.

I would probably rename the field from FIRSTNAME to TITLE to make it a little clearer. Or do you call your Operations Manager "Opie", for short :-)

[Mike Konoff]

RE: CASE funtion update

Ah...I see. It defaults, and then that's it. OK, I'll make another database to get the value I need.

Good idea.

Thank you,
Mike

[CALocklin]

RE: CASE funtion update

Mike, instead of using the OnSave event, try either the CanSave RECORD event or the OnWrote FIELD event.

I recommend the OnWrote event because the change will happen as soon as you leave the CODE field.

Using either the OnWrote or the CanSave event instead of the OnSave event means you can simply say:
IF code = 'whatever'
parentform.firstname_obj = "Manager"
END IF

(the above assumes that the form object which holds the 'firstname' field value is called 'firstname_obj'.)

With OnSave, you will put the form back into change mode when changing the field and you will have to include a 'parentform.commit()' command. Or, if using table mode, you will have to put the table into change mode, make the change, save (end) the change, and re-synch the form.