Hi,

I am thinking of setting up value list based on field values, but I am not sure my procedure is correct, or even recommended. I do not like to allow users modification of standard FM value lists.

My thoughts are:

1.- Create a ValueListNames (VLN) table. This table would hold the value list names.

2.- Create a ValueListData (VLD) table. This table would hold the values associated to the ValueListNames table.

3.- Link both tables using the VLN key, to allow me to create records in VLD linked to VLN.

4.- Create a layout in VLN with 2 portals. The first (portal1) one would be a self relationship to show all records in VLD. The second one (portal2) would show the related records from VLD. The user would clic one VLN record in portal1 and portal2 would show the related records, allowing creation, deletion, or modification of records. I am planing to create scripts for all this tasks.

Questions:

1.- Does this sound good practice?

2.- Is it OK to use 2 different tables as opossed to using only one? (the alternative would be to have only one VL table, with one VLName field, and one VLData field for each record; I do not find this a reasonable alternative, but...)

3.- If I go for the one table option, I would have two or more different records with the same value in the Name field (the value list name). How do I show in a portal only unique values? (please do reply to this question although 2 tables might be the preferred option).

For instance:

Record1

VLName: Color

VLData: Red

Record2

VLName: Color

VLData: Blue

Portal

Color

Related portal

Red

Blue

Thanks in advance

Creating 2 tables for your value lists seems like overkill to me. I can't see any advantages to it. Just make one table with a field for the name of the value list and 1 field for the value. The value list name (I assume) won't even be used for anything other than your reference.

And don't worry about 2 occurrences of the same data in 1 field but in different records...FM will only display it once in the value list.