Not resolved, just closed, See me next post, below, for more information

I have a multi-select drop down list which comes in to a variable, &STUFF, as

'item1' OR 'item2'

, which I use as a filter (WHERE FILELDNAME EQ &STUFF) This equates to

WHERE &STUFF EQ 'item1' OR 'item2'

. This works fine.

The issue is passing this via a drilldown (Simplified: TYPE=DATA, COLUMN=RPT_STUFF, TARGET=BLANK, FOCEXEC=IBFS:/WFC/Repository/Folder1/MyFex.fex( STUFF=&STUFF ); Then what to do when it comes in as FOC_NONE, without the quotes? Yeah I'm stumped.

I hope that explains it well enough...

Thanks In Advance, Doug

This message has been edited. Last edited by: Doug,

quote:

he issue is passing this via a drilldown (Simplified: TYPE=DATA, COLUMN=RPT_STUFF, TARGET=BLANK, FOCEXEC=IBFS:/WFC/Repository/Folder1/MyFex.fex( STUFF=&STUFF );

Hi Doug Try QUOTEDSTRING with the Variable.

 &STUFF.QUOTEDSTRING
FOCEXEC=IBFS:/WFC/Repository/Folder1/MyFex.fex( STUFF=&STUFF.QUOTEDSTRING )
 

Thanks for your suggestion Chaudhary,
Hoever the use of QUOTEDSTRING is fine when the data comes in quoted, but FOC_NONE, the default, isn't quoited. Thus it kicks out and unknown field error.

I'm reverting back to the basic. So this post is obsolete, I'll close it

Doug,

When using &VAR.QUOTEDSTRING, instead of using FOC_NONE as default non-selected value, try to use _FOC_NULL.

Thanks Martin.

This set of procedures was built "on the fly" / based on a POC. So, I scarped the whole the whole things and rebuilt it mostly in the GUI, I needed to *** some DM to display 'user friendly' text for the heading.