How Can i add values of two value list in the third value list.

If your first two Value Lists are based upon field contents, you can create a calculation (text) which combines these two text fields with:

TextField1 & "

Using the ValueListItems function you can get the values from the 2 lists. Make a calculated text field that concatenates the 2 with a Paragraph mark between them. Use this field for your new value list.

Ralph said ...Using the ValueListItems function you can get the values from the 2 lists.

I have never gotten this to work - combining two value lists using the ValueListItems function. I would be interested to know if this can indeed be made to work. I just tried again and can't produce any results on it.

BTW, it *might* be more resource-efficient to simply use a third text field instead of a calculation. Since you are using FM7, you can set a third text field (not displayed anywhere) with an auto-enter calculation (unclick 'Do Not Replace Existing Values'). This field will change according to your entries in Field1 and Field2 (using the same calc I indicated above). Then base your new Value List on this field. If data already exists in your solution (prior to adding the auto-enter calculation), you would need to force a recalculation through your records. That would be easy if you want to know how.

Resource wise, I'm unsure which would be the most efficent - a calculation or a standard field. Maybe others can answer this question for us?

I just did it with the following calculation: ValueListItems ( Get ( FileName ) ; "ValueList1" ) & "

Yes of course. I stand corrected. I was thinking of 'display' of a calculation using both Value Lists. In which case, the resulting calc would list the same item twice (if in both Value Lists) and wouldn't even put them in alpha order. But for creating a new Value List, this is certainly a way to go. Thanks, Ralph.

alimrb, either Ralph's or my original calculation will work. Which would be the most efficient method remains unclear.

Upon considering the various options, I have concluded that using a standard field with Auto-Enter calculation to be the most efficient (using my first calc). There is no need for another calculation at all. Then simply base your new Value List on this third (invisible) standard field.

I have been doubting the need for calculations for several weeks. FM7's ability to auto-enter (and change) data on the fly, eliminates the need. This is a prime example where a calculation can (and should) be replaced with a standard field. And I would bet most calculations could be eliminated altogether by using auto-enter on regular fields - and would save resources.

If I'm going off in the wrong direction, I would love to be straightened out.