Calculated Attribute

vinsnash

I have an age attribute that I want to calculate not entered. I use the rule:

NSCPers.Age=Age(NSCPers.BirthDate)

During the create operation I enter NSCPers.BirthDate using the calendar provided but age is not calculated or displayed.

There are two more attributes after age that use age to determine the initial values but can be changed. Both have a list of possible values in drop downs but neither of these is accessible. After NSCPers.BirthDate is entered the three fields to calculate are skipped.

I must be missing something in the attributes configuration?

Thanks for any help.

tford

If you go back into the record after creation is NSCPers.Age calculated properly and shown?

vinsnash

Yes, all three calculated fields are correct. How to I get them to display at enter time?

Thanks for the help

Vins Nash

tford

Try making it a dynamically recalculated rule.

vinsnash

I'm not sure how to do that. These are rules I've set up in the in the business space editor under "Edit Rules"

NSCPers.Age=Age(NSCPers.BirthDate)

If NSCPers.Age<13 Then NSCPers.Branch='NLCC'

If NSCPers.Age>12 Then NSCPers.Branch='NSCC'

If NSCPers.Age > 12 and NSCPers.Age < 18 and NSCPers.Gender = 'Male' then NSCPers.MemberType = 'G' ELSE If NSCPers.Age > 12 and NSCPers.Age < 18 and NSCPers.Gender='Female' Then NSCPers.MemberType='W' ELSE If NSCPers.Age > 18 and NSCPers.Age < 21 Then NSCPers.MemberType = 'D' ELSE If NSCPers.Age > 20 Then NSCPers.MemberType='U'

Thanks for the help

tford

Search the forums on the word 'dynamic' in the last week or so. It's been asked / explained twice.

Tom

vinsnash

I've seen a lot of posts on calculated fields not displaying or exhibiting strange behavior. Through a lot of trial and error I have discovered two conditions. I have two fields on a form that ask for gender and birth date. 4 object attributes immediately following those two are determined by those two values, gender and birth date.

Form controls that are used to calculate other attributes must lose the focus before the calculated fields are display. I was using the mouse to move to the next field after the four calculated fields and that was not causing the necessary loss of focus. Using the tab key after entering the birth date did the trick. All four fields displayed immediately with correct values in read only mode.

Also I found that tabbing is inconsistent with Mozilla but works correctly with Explorer. Using the calendar control to select a date also sometimes causes inconsistent results. Keying in the date and using the tab key is always consistent in my case.

tford, maybe you can spread this info around.

Thanks for your help