yes

If you right click on the button that is created to run the dropdown, you will see some settingfields, one of them is the place where the output needs to be presented, you can select an iframe or window, that should be it. (I have the software not available jet, so this is done by head)

What Prarie does is what I do too, but according to the manual you should not have to.

Make sure that your procedure is returning two values and the hold format is XML.

TABLE FILE CAR
PRINT DST.COUNTRY
BY COUNTRY
ON TABLE SET HOLDLIST PRINTONLY
ON TABLE PCHOLD FORMAT XML
END

The BY field would represent the value for the list and the print field would represent the display value.

Is the output format in the fex you are using to populate the dropdown box XML? If not, that may be why you are getting a new window.

The syntax should be something like this:

TABLE FILE GGSALES
SUM FST.PRODUCT
BY PRODUCT
ON TABLE PCHOLD FORMAT XML
END

Please check the Developing Reporting Applications Manual, the section on 'Customizing Dynamic Parameters' for details on this.

This technique works very well and it is very effiecient as you can also put WHERE clauses in the code. We use it a lot.

Thanks for the help!
it's working better now, as I'm created a focus database file and building the dropdown list from that. Unfortunately it's not in alphabetical order!

How do I make it show up in alpha-order?

here's the fex that builds the foc file. When I change it to html, it shows it alphabetical!

APP HOLD ~metadata
FILEDEF LKP_SALESMAN DISK G:\IBI\APPS\~metadata\lkp_salesman.FTM
TABLE FILE LKP_SALESPERSON_MQT
PRINT
SALESPERSON_NUM
BY LOWEST SALESPERSON_NAME
HEADING
""
FOOTING
""
ON TABLE SET PAGE-NUM OFF
ON TABLE NOTOTAL
-*ON TABLE PCHOLD FORMAT HTML
ON TABLE HOLD AS LKP_SALESMAN FORMAT FOCUS
ON TABLE SET HTMLCSS ON
ON TABLE SET STYLE *
UNITS=IN,
SQUEEZE=ON,
ORIENTATION=PORTRAIT,
$
ENDSTYLE
END

Nevermind, it's perfect using Gizmo's example.
Thanks everyone!

I hope IBI puts Gizmo's example in their documents somewhere, that's perfect!

Actually, IBI already has this in the documentation and would be very close to what I have. The one exception is that I think they use SUM like Ginny did. I usually use PRINT DST.fieldname since this will translate to distinct in a SQL request which can improve performance.

I agree, Gizmo. I just copied the code out of the manual. I would use DST. as well, especially against a relational data source.

And, Jason, the example is the the manual, only with an FST. instead of a DST.

Please check the Developing Reporting Applications Manual, the section on 'Customizing Dynamic Parameters' for details on this. You will see the example. Also how to do chained boxes using procedures.