In webfocus report I put in combobox's for different fields with relation to car.mas
If I select ENGLAND in country field I wish ti display only companies in england and the models made by those companies.
How can this type of cascading be achieved?

This message has been edited. Last edited by: FP Mod Chuck,

In HTML Composer, you can chain those controls on the parameters tab.

I am using a user defined parameter for binding control to the particular combobox but somehow I want the other comboboxes to also reflect the required data
I saw one way was to use Explicit controls in properties in settings within HTML composer

Asamant59

Chaining is the way to do what you want. It is all done through the parameters tab as Webp5622 described...

I don't know if chaining is any easier on newer versions of Developer/App Studio, but this is how I do chaining.

First, I make small external procedures which will populate my parameters.

For example Parameter1.fex looks something like this:

TABLE FILE (TABLE1)
SUM
FST.FIELD2
BY FIELD1
ON TABLE SET HOLDLIST PRINTONLY
ON TABLE PCHOLD FORMAT XML
END

Then I have Parameter2.fex that looks like this:
-DEFAULT &FIELD1 = 'FOC_NONE'
-SET &FIELD1 = IF &FIELD1 EQ 'FOC_NONE' THEN '~' ELSE &FIELD1;
TABLE FILE (TABLE1)
SUM FST.FIELD4
BY FIELD3
WHERE FIELD2 EQ &FIELD2
ON TABLE PCHOLD FORMAT XML
END

Then when you are building your parameters in Composer, you populate them with those procedures (so your first parameter would be using External Procedure Parameter1.fex, second using Parameter2.fex), and then chain them.

The easiest method for chaining is by adding master files and generate embedded TABLE requests on those.

You'll only want to do that on masters that describe small(-ish) tables though, but that seems to be the case for the OP.

Using external procedures that output XML, like you do, is a more advanced use of chaining.