I have a couple of value lists defined to use values from fields in 
another table, and it seems that causes problems when I want to do a 
search using those value lists. There's no problem if the value list is 
set to use all the values from the other table, but when I only want to 
use the fields that are related to my main table, I get "no values 
defined" in search mode. Any way to avoid this? Or do I have to 
"hardcode" these value lists in stead?

-- 
Thomas Hansen   :   th(at)ambolt.no   :   http://www.ambolt.no/

In article <violon-0ABBDF.12380819122005@sunsite.dk>, Thomas Hansen
<violon@online.no> wrote:

> I have a couple of value lists defined to use values from fields in 
> another table, and it seems that causes problems when I want to do a 
> search using those value lists. There's no problem if the value list is 
> set to use all the values from the other table, but when I only want to 
> use the fields that are related to my main table, I get "no values 
> defined" in search mode. Any way to avoid this? Or do I have to 
> "hardcode" these value lists in stead?

Relationships only work when there is key data in the parent record to
match to related records. During Find mode there is no parent record
key data, so there is no valid relationship and therefore no related
records.

One way around this is to simply have a separate layout for processing
finds. The field can then use a separate value list that simply lists
ALL possible values from the field other file / table. Of course this
is very painful if there are hundreds of possible options.

The other way is for you to use Global fields into which users type the
necessary Find data, then when they click a "Process Find" button a
script transfers the Global data to proper Find requests and processes
the Find. You'll need to have a separate copy of relationship set-up to
match the Global field instead of the record field toget the value
list.

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