Here is an example of using the Child handle when getting a UDF value in purchase order.

retVal=0
itmCode=""
oItmSvc=0
Notes=""
Desc=""

retVal=oBusObj.GetValue("ItemCode$",itmCode)
retVal=oBusObj.GetValue("ItemCodeDesc$",Desc)
oItmSvc = oBusObj.GetChildHandle("ItemCode")
set oItmSvc=oSession.AsObject(oItmSvc)
retVal=oItmSvc.Find(itmCode)
retVal=oItmSvc.GetValue("UDF_PURCHASE_ORDER_NOTES$",Notes)
If Notes <>"" Then retVal=oBusObj.SetValue("ItemCodeDesc$",Notes)

End Sub

With GetChildHandle the Find line shouldn't be necessary...?

With GetChildHandle the Find line shouldn't be necessary...?

"Shouldn't be" is the keyword but sometimes i find that you have to force the child object to be on the correct record and this is done either by setting each key value followed by Find or my using ReadAdditional without any arguments to force all child objects to read the "correct" record or pass the field used for the child object as the first argument to force just that child object to read the "correct" record. This should be done prior to using GetValue from the child object.

Yes... "should" is not the way things always are indeed.  After your comments (here an in previous posts) I have made a mental note to try ReadAdditional the next time I have issues with a child handle.