Relational Value list...help!

[idcmktng]

using fm7

Pretend I have not been using since v1.0

I have an xl file set up as follows:

style model xprice xaprice sprice saprice

Arthur dining 75 100 na na

Arthur pub na na 25 40

Arthur whatever na 30 na 39

Trevor dining 99 115 na 100

blah blah blah

What I want to do is have an order entry database where when I select "style" it will give me the list of styles (easy)

What I can't figure out is how to have a value list based on the model I just selected...i.e. to give me only "dining, pub, whatever" for "Arthur". Then I want to have a value list based on the 4 price combinations available for the previous two selections.

I've tried everything and keep going around in useless circles. The documentation on table relationships is pretty confusing :

Anyone have any suggestions on how to achieve this? I've been working on this all day and I'm cross-eyed.

Thanks...

Kyle

[LaRetta]

Hi Kyle,

You need conditional value list. You can do a search here for many examples. The idea is this:

Create another table occurrence of your table, maybe called Styles. Join Style to Styles::Style. Establish a Value List based upon values from field. In top popup, select your Styles TO and select your Styles field. Below, only include related values and select your original table.

Actually, it doesn't seem to matter which TO you specify above and which below, ie, it seems to work exactly the same if you select your original table above (with its field) and select related values to your Styles TO, at least in a self-join. I've been wondering how the results may vary with different TOs and POV from different directions. But in your case, it doesn't matter.

You'll need to repeat this process; joining your next category and filtering the conditional popups in the same manner.

LaRetta :wink2:

[idcmktng]

I forgot to throw the wrench in the mix...it must work with repeating fields. I can get the first rep to work, but the subsequent reps keep adding to the value list even if the option is not available for the group in that particular repetition. Then it doesn't calculate a price.

Attached is a sample of what I'm trying to do. Would I need 15 different tables for each rep?

I'm about to lose my hair on this one. It has to be something simple I'm over-looking.

Thanks again

~Kyle

tmpo_items.zip