Shrinking/Expanding/Dynamic Value List

I've been digging around here and the posts on conditional value lists have been helpful.

i.e. helpful value list post

However, I think this one is a hair different...

Here's what we originally started with:

A single table containing a value list of 25 CUSTOM values, cap warning calculation fields for each entry in the value list and supporting summary fields for the calculations.

Field 1, "Sessions", displayed the values of the pop up list and the other calculation fields would display "CLOSED" once a value had been selected from the pop up list in ten separate records. Therefore, if we selected value A02 in the pop up list in ten records, the cap warning field for value A02 would display "CLOSED".

Custom values for pop up list "Sessions" field:

A01

A02

A03

A04

A...

Cap fields:

field = [cap_warning_session_A01] - (cap warning for value A01 in pop up list)

field = [cap_warning_session_A02] - (cap warning for value A02 in pop up list)

field = [cap_warning_session_A03] - (cap warning for value A03 in pop up list)

field = [cap_warning_session_A04] - (cap warning for value A04 in pop up list)

...

This works fine. However, we now want to move the solution to IWP and we want the value list to ONLY display values that aren't "CLOSED". In the example above, A02 would not be displayed in the pop up list. However, if a record that was holding an A02 value was changed to A01, then A02 would need to be displayed in the pop up list again.

The idea was to create a second table to hold 25 records, A01 through A25 and link the tables via the "sessions" field in table 1 and a "sessions" field in table 2. The next step was to create a second field in table 2 called "session_display". "Session_display" would be an "Auto-enter calculation that replaces existing values and evaluates always". And the calculation was.. If ( table1::cap_warning_session_A01 = "CLOSED" ; "" ; "A01" ). Finally, the custom value list in table 1, "sessions", was replaced with VALUES FROM FIELD "table 2::session_display".

The problem is that the value list in table 1 only evaluates if we make a change in the "sessions" field in table 2.

I think we're on the right track, but just missing a piece. Any suggestions would be greatly appreciated.

Thank you FM Forums!