oh well sounded good on paper anyways. the information in the popup field if to long gets cut off.   

Quote:


So you have the KeyField, I believe that is sequential unique number that you might be deriving from @number or Globalvalue.  Good thinking... better than I suggested to combine two names as this will be always unique. If you have unique key value in each record of subform Equipment List, you may represent the key in say String of five digits with filling up with zeros up front if it is less than five digits long...such as 00005 or 00324.

You get the string in form dispatch using @xlookupall, and it would be like equipment00124 unless you are prepared to put couple of more elements. Eventhoght display will show the number, when you will choose the item, Equipment_Type element will take only equiment name and key will go to another element or for better presentation and readability you may present list as   "Equiment         00124"  format that is more pleasant to look at. Just a thought.

Flip, Glad to know that it worked out for you as you wanted it to.  I was thinking about how it could be done without changing any structure or making any new field. Since now you already made the changes and added an extra-element or modified and made it work, this discussion is just academic value and may be just theoretical. I believe the following should work if we call the above subroutine after picking up equipment on element exit event. Subroutine goes in the Global Code.

var vEquipmentInfo as String
vEquimentInfo = @xListValueAll(@FN, Company, "Equipment_List!CompanyName","CompanyName;SerialNo;Model")

vEquipmentInfo = @Repleace (vEquipmentInfo, @newline ( ), ";")

Subroutine Populate_fields()
var t as array[20, 3] of String  //company could have upto 20 equiments
var i as Int

//Populate Array

i = 1

While @len (vEquipmentInfo) > 0
     t[i,1] = Split (vEquipmentInfo, ";")
     t[i,2] = Split (vEquipmentInfo, ";")
     t[i,3] = Split (vEquipmentInfo, ";")
     
i = i + 1



//Loop to find the value of Equipment and when found assign value of serialNo and Model

For i = 1 to 20

      If t[i,1] = Equipment
         {
           Serial = t[i,2]
           Model = t[i,3]
           i = 20
         }
     Else
           i = i + 1

Next      

End Subroutine

===============

I did not debug the above codes and did not check the names of elements but concept and logic should be understandable.

I would like request the Lantica Development team to include the availability of simple function, in which one could combine two or more external key elements to make it Unique to be used in some of the x-family functions, that will obviate the need to change the structure or add any additional element to make an Unique key.

May be I should request this in a separate link.