I have a pop-up menu on my main table that displays an option for the
user to choose sound type (low, medium, high). The pop-up pulls from a
different related table, which holds the sound values and
descriptions:

Main Table
fields:
sound description (pop-up menu, pulls from Sound Lookup Table,
displays description only)
sound value (calculated field, pulls sound number value from related
Sound Lookup Table)


Sound Lookup Table
fields:
sound value (1,2,3)
sound description (low, med, high)

The relationship is through "sound description" fields. I have a
calulated field in the Main Table which pulls in the corresponding
value according to what sound description users choose in the pop-up
menu.That way, the user sees only the description in the pop-up (low,
med, high), but I can store the value in my main table, which I need
to use for an export - and I need the number value code of 1,2, or 3
rather than the description of low, med, high.
So far so good!

But I want to sort by the value field, so that my pop-up menu is
ordered low, med, high (rather than the current alpha sort: high, low,
med). And the only way I can see to do this from the pop-up dialog is
to display values from both fields...and I'd rather not do that.

Any ideas?

I have a bunch of these menus to make, some with rather long lists.

Much thanks to this great group!
-learning cat

In article <1179374918.864274.26680 (AT) w5g2000hsg (DOT) googlegroups.com>, cat
<cathytyner (AT) gmail (DOT) com> wrote:

Maybe you're using a simplified example, but if the only values you
need in the pop-up menu are "Low", "Med" and "High", then why bother
using a Value List via a Relationship from another table?

Just define a "Volume" Value List using those values typed directly
into the Define Value List window, then the pop-up menu will display
them in the same order as you type them.

You can possibly get rid of the Sound Lookup Table entirely since the
Sounds Value can be Calculated from what the user chooses in this
pop-up menu.
eg.
Sound Value Claculation, Number Result, Unstored
= Case (Volume = "Low", 1,
Volume = "Med", 2,
Volume = "High", 3,
)

If the Sound Lookup Table is actually necessary for something else,
then you can still have a Relationship link based on the Volume field
to retrieve the Sound Value.


Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)

On May 18, 11:46 pm, Helpful Harry <helpful_ha... (AT) nom (DOT) de.plume.com>
wrote:
Thanks for responding -

I have indeed used "Case" as you suggested here - for these small pop-
up menus, it works fine (it was a simplified e.g.)! But what about for
a long list of options, where I need to display the description only,
and store the value, but sort by the value list? I guess this just
isn't a common issue - I can see that most folks would want an alpha
sorted description field most of the time, rather than a custom sort.

Any ideas?

Thanks again for your help.
-cat

In article <1179557675.339709.242760 (AT) o5g2000hsb (DOT) googlegroups.com>, cat
<cathytyner (AT) gmail (DOT) com> wrote:

You can still have a second table to look up the "1", "2", "3" data,
but still store the pop-up menu values as a normal typed-in Value List.
ie.
Sound Volume Text Field formatted to use a Value List of:
"Low", "Med", "High"

SoundRelationship Matches Sound Volume to
SoundLookupTable::Volume

Sound Value Calculation
= SoundRelationship::Value


When the user chooses "Med" from the pop-up menu, the relatmship
matches it to "Med" in the Sound Lookup Table and the corresponding "2"
can be retrieved in Sound Value.

BUT, because the Value List is typed in using the order you want, the
pop-up menu is not alphabetically sorted.




Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)