>>>Koen,
>>>
>>>What I want to achieve is this:
>>>
>>>Say an invoice form needs to call a lookup form of items. When item lookup form comes up, it allows users to select several item records. I would like for the selected item records be passed back to the invoice form in the form of a cursor.
>>>
>>>Currently, my lookup form class only allows a single selection, which I dump into the calling form as a data object (SCATTER MEMVAR NAME oCallingForm.Returndata )
>>>
>>>Thanks!
>>>Dennis
>>
>>
>>oCallingForm.Returndata could also by an array or a collection. That way you can scatter name more than once and return more than one record
>>
>>But remember the dangling datasession
>
>That is the reason I prefer ref arrays as parameters to a function for such tasks:
>data out, fieldlist [in/]out, parameter array to switch on memo, define alias and so on.
>And single operations like Select SQL or copy to depending on memo handling if done without "in" fieldlist.
>
>my 0.02 €
>
>thomas


Ideally, he should be passing an array of pk's instead of records. The calling form can easily handle that