In order to support the re-use of a value list on layouts of several different

tables (let's call them A.fp5 and B.fp5), I've created a single table (let's call

it List.fp5) containing those values. A.fp5 and B.fp5 obtain the values

via a pop-up list, set up by defining pop-up asoption "Use values from field, specify table...List.fp5."

So far, so good.

The undersireable behavior is that when a value is chosen from the pop-up on

A.fp5, a new (and thus duplicate and useless) record is create in List.fp5.

What's up with that? How do I prevent it?

Thanks for your help, folks.

-- Pat

Strange behaviour.

Make sure you do not use in your File A and B a related file from List file.

If so, not only will you have duplicate, but you will also have some suppresions.

Did you made a relation with creat new records from this relationship ?

Yes. A.fp5 has a relationship to List.fp5, and it is checked "Allow creation

of related records." When I de-select "Allow creation of related records,"

the pop-up in A.fp5 does not function at all.

-- Pat

What is your relationship definition, and why would you use it for. And is the field in File A a related file from List File (check in layout mode that it doesn't have a ":: " before the field name

Ah, I see that I've not provided enough information about the table structures.

A.fp5 fields

------------

customer_name (text)

org_type_id (number)

A.fp5 contains relationship A.org_type_id<->List.id (allow creation of related records)

List.fp5 fields

---------------

id (number)

description (text)

Layout of A.fp5 shows

---------------------

customer_name

::description (value list sourced from List.fp5 based upon A.org_type_id<->List.id relationship)

The "description" field, therefore, is not "native", so to speak, in A.fp5,

because to do so would not support normalization and, therefore, reuse of

the list by multiple tables such as B.fp5.

-- Pat

OK, this is clearer now.

You cannot use the ::description in A or B, because doing so, you are simply creating or modifying ::description, that is to say that while in File A, you are modifying List file. Do you get it ?

What you have to do is creating a field in A or B with "description", then in layout mode define the field to use the list from records from List File. There is in fact no relationship needed to do so. You just use the records from another file...

Now, to have two different lists to appear, just create two fields in List File :

description A

description B.

Then in File A, use the list from description A from File A

in File B, use the list description B from File B.

If you had to modify this list, just use the checkbox, modify or add to list while in the format menu for fields "description" in A or B.

You could also use conditional value list but I don't think you need it.

Do not hesitate to post back if this is unclear.

To make it clearer. hERE IS ATTACHMENT