I have a FM7 file(&table) "tableChooser" and file(table) "software".

The user logs into "tableChooser", his/her name is set in a field "login", then s/he selects (check boxes) one or more files(tables) to open, clicks a button that then opens whatever file(s)(table(s)) are chosen.

"tableChooser" has a global storage number field "gConstant" set to "1", which is related to (=) "software::gConstant" (with the same settings as in "tableChooser::gConstant"). I don't think there is anything in this relationship causing problems; just mentioning it.

In "software", I have a field set up this way:

software::created_by

Text

Auto-Enter

Calculated value = tableChooser::login

Do not evaluate if all referenced fields are empty UNCHECKED

Do not replace existing value of field (if any) UNCHECKED

Validation:

Validate ... Only during data entry

Allow user to override during data entry CHECKED

No requirements.

When I create a new record, software::created_by is not populated, however when I run a duplication script, this record properly populates the field:

Set Field [software::created_by; tableChooser::login]

I realize the mechanism is different; just showing this so that the relationship can be shown as working. Ideas? Thanks.

Ken

"..."tableChooser" has a global storage number field "gConstant" set to "1", which is related to (=) "software::gConstant"..."

The right hand side of the relationship needs to be a stored indexed field. It cannot be a global.

Try changing the operator to x.

Outstanding, that worked great! At this point, should I even bother with changing the storage type, since "x" works? Thanks.

On a related note, I have another file/table (hardware) related to the file/table "tableChooser" in the same way, and the created_by field works in this case. More digging to do there I suppose....

Ken