90% of the time I use this method to display a popup of

items for the user to click on and pump right into the

form.

A Button-]Quickevent-]Popup-Control(@window)-Property(QBFLIST)

I have forgotten how to accomplish the same thing when

calling a Popup from a script. x=Popup(@window,,name) Thanks Homer. </QUOTE> —- === At 07 OCT 1999 04:28AM Tony Marler @ Prosolve Software wrote: === <QUOTE>Can you restate the question because I don't follow ? Its fair to say I was up until 1:30am trying to lean AMin7 arpeggio riffs last night so perhaps its just me. Tony </QUOTE> —- === At 07 OCT 1999 05:10AM Oystein Reigem wrote: === <QUOTE>(Networking Products? Bruce Cameron or Homer?) 90% of the time I use this method to display a popup of items for the user to click on and pump right into the form. A Button-]Quickevent-]Popup-Control(@window)-Property(QBFLIST) I assume what you do here is to display a popup that returns one or more record keys. And then you put the key(s) into the window's QBFLIST, like if the keys were a result list from a QBF search. Then you get the record for the first key displayed in your window, you can change the record if you like, and you can browse back and forth if you have more than one key. For the popup to return more than one key it would normally have to be a multi-select popup. But as far as I know a multi-select popup returns a @VM-delimited list of keys, and QBFLIST needs a @FM-delimited list. So I think the above would fail with multi-selection. Therefore I assume you have a single-select popup and only one key. Which raises the question why you use QBFLIST which typically would be used for a result list, not a single key/record. But never mind. I have forgotten how to accomplish the same thing when calling a Popup from a script. x=Popup(@window,'',name) Try List=Popup( … ) * convert delimiters in case multi-select convert @VM to @FM in List UnUsed=Set_Property( @Window, "QBFLIST", List ) - Oystein - </QUOTE> View this thread on the forum...