using a global field for a value list

[shogunjp]

Any suggestions?

Reason: This is a non-profit membership database, it generates a list of current board members by searching the database for the checked board member option, it then compiles the persons full name and places it into a Global field, it repeats this for all current board members. I then want that global field to be the basis for a value list, so we don't have to alter the value list everytime the board member list gets changed...

Thanks

[markpro]

You don't need a global field. Create a calculated field for full name. Call it "Board_Member". Example calculation:

Case [checkbox="Yes",First_Name & " " & Last_Name]

Your Value list then is based on Field contents of the "Board Member" field.

[shogunjp]

thanks... hmm.. I am feeling a bit dumb right now.

[shogunjp]

It didn't work, the check box and the name fields are not located in the same database, (they are related through an ID number) Because of this, filemaker can not turn indexing on. Therefore, Filemaker can not turn the calculated field into a value list.

[markpro]

How about creating the field in the other database and looking up the values?

[markpro]

Another quick thought: What if the Check box field is actually in the same database as the names, and you use a relationship to display it in the file it currently resides in. This way the "name" field could be indexed because it is no longer depending on a related field.