In the above Setup layout, on the left column is a hard coded list of membership 'types' (Yearly, Honorary...etc)

.

These Memberhship 'types' are accessed in the main program via a dropdown listing. Each member has a membership 'type'. The dropdown choice is used to calculate what the membership dues are for that membership 'type'.

This works well.

However, I would like to replace the 'hard coded' dropdown list of Membership 'types' (Yearly, Honorary...etc) with global fields or $$variables.

The purpose is to allow the user to define the membership 'type' (In he setup layout above) by, for example, replacing '50 Year' with '40 Year'. Then (and this is the tricky part), that 'new' Type would show in the dropdown.

I have tried using global fields and they don't seem to work. I have tried putting $$variable in the dropdown list and that won't work.

I have thought of using a portal but that accessed a single field and that doesn't seem to work with the dropdown.

I am stuck and would appreciate any ideas.

Thanks

Ron

ron, i know i am guilty of Being Vague, but i really dont get this question!

you want a "SAVED CHANGE" from globals to make a change to your "HARD CODED"dropdown list of Membership 'types' (Yearly, Honorary...etc)

I have tried using global fields and they don't seem to work. I have tried putting $$variable in the dropdown list and that won't work.

ron, i know i am guilty of Being Vague, but i really dont get this question! you want a "SAVED CHANGE" from globals to make a change to your "HARD CODED"dropdown list of Membership 'types' (Yearly, Honorary...etc)

I think i get what you are saying now. You want " ALL / ANY " User to be able to change the Blue text in the main table , in essence updated the related table?

is that correct?

ian

Ahh.. the Bahamas! It is snowing here in Western Washington. ugh

Yes, I want the user to be able to change the 'blue text' in the screen shot and have those changed values show in a dropdown / popup list. If I "can't get there from here" I can stop trying... :laugh2:

Cant you enable "Editing" and "allow other entries" in the value list

Allow certain permissions to be able to change the TO specific to value list.

I know for a fact that you should have a TO specific to the Value List for this sort of stuff. I am no Expert, but if you do that, you should be able to edit/ add/ delete

from the value list.

Hope that helps somewhat.

-i

*laRetta may know more. Hope she has time.. I know for sure Comment knows the answer... : )

Cant you enable "Editing" and "allow other entries" in the value list

Allow certain permissions to be able to change the TO specific to value list.

I know for a fact that you should have a TO specific to the Value List for this sort of stuff. I am no Expert, but if you do that, you should be able to edit/ add/ delete

from the value list.

Hope that helps somewhat.

-i

*laRetta may know more. Hope she has time.. I know for sure Comment knows the answer... : )

Yes, I could enable editing of the dropdown but in calculating if a Membership Type pays dues (for example), the script that uses the selected Membership Type (Yearly for example) needs to be evaluated. An example would be "If MembershipType="Yearly"...

If I allow editing, "Yearly" may become "Annual" for example, and then the script won't work. That is why I thought I could substitute Global::Type1 ... Global::Type2 etc for the hard coded field names. That works but I can't get the 'content' of Global::Type1 into the dropdown.

I 'got' part of it to work (Thanks to Briandunning.com).

BD has a custom function (ValueListSelectedIndex) which returns the index of the selected Value List. This allows me to remove the hard coding from my script (which looks for IF Members::Type="Yearly" and replace it with the variable that holds the index. Now, I just need a way to get the Setup::MembershipType values into the Value List...?

For the first part of your problem, why not use a value list based on the field, rather than hard-coded?

For the second part, create a relationship from member to membership types based on the field, and you can then look up or display all the related options for that type. Does that make sense?