another way to handle this would be to use a launch form that contains frames and each selection launches a fex into a separate frame where values are displayed as hyperlinks. All values are then passed back into the original frams where the report is launched. A little confusing, but I absolutely hate trying to get chaining work all of the different ways I need so I avoid it. Chaining is probably an easier technique, but I feel it to be too restrictive. This technique gives amazing flexibility. For those who would suggest that "We only fear what we don't understand" you're probably right, but I don't have much desire to understand chaining any further. I can give some additional info if this is something you may be interested in.

Not a huge fan of chaining at the moment, but if my NFR turns up I might just give it another shot. I think we have similar needs.

I'm hoping the backroom boys will soon be adding a feature to allow parameter passing to fexes that generate the DDL contents. This will save me jumping through all kinds of hoops with hold files etc.

So for now I just do it the quick and dirty way. DDL1 calls DDL2 calls DDL3... and
I don't even bother with frames. When that param passing feature arrives I have the code already waiting to do its mojo!