I have code that works that calls a drill down:
TYPE=HEADING,
LINE=2,
OBJECT=FIELD,
ITEM=1,
TARGET='_blank',
FOCEXEC=app/bbbrovr1.fex(PRODGRP='&PRODGRP.EVAL' PRODLINE='&PRODLINE.EVAL' GEOGRAPHY='&GEOGRAPHY.EVAL' AREA='&AREA.EVAL' QTR='&QTR.EVAL' WFFMT='EXL2K' ECHO='ALL'),
$

This works if none of the filters are set. When some of the variables are set I get this error:

-SET &PRODLINE='FOC_NONE';
-SET &MIXED='';
-SET &CLICKED_ON='';
-SET &QTR='A';
-SET &ANALOG='';
0 ERROR AT OR NEAR LINE 24 IN PROCEDURE _bbbrovr1
(FOC318) A FIELD FORMAT IS NOT ALLOWED IN -SET: &SIGNAL''='';

Note that the focecec name in the error messsage has _ in front of the name of the fex.

The code echoed above is not in the fex being called.

Anyone encounter this before?

Thank you for your assistance.

Secret,

If you view a procedure trace the underscore prefix will become clear to you.

As for the error detail that you say isn't in your code, again, the best process for finding out what is occuring is to turn on a procedure trace for your process. A word of caution though, if you have a lot of people running procedures at the same time your trace is on, you may find the response times are affected. Therefore only have the trace turned on at the time of your run.

You do not have installation information in your signature so I can't tell you how to turn on the procedure trace as it changes between 5.3 and 7.1.

Get the trace and view it, it is quite enlightening. If you can't fathom it then you have two choices. Put it up on the forum for assistace or contact IB. Depending upon the content you might choose the latter option.

Some possibilities that immediately jump to the fore is the existance of an identical named fex towards the beginning of your APP PATH (use APP SHOWPATH within your code to view it). The other is, in your drilldown fex do you DEFAULT ALL of the variables you use or will pass to it?

Good luck

T

In addition to Tony's suggestions, I would try the following:

Usually, the fex name is just the fex name in upper-case, BBBROVR1.

I would remove passing the ECHO variable. Just set the ECHO in the drilldown program.

I would also break the drilldown command into multiple lines using the continuation character, just in case the line with the substituted values is too long for the parser.

It would look like this:

FOCEXEC=BBBROVR1( \
PRODGRP='&PRODGRP' \
PRODLINE='&PRODLINE' \
GEOGRAPHY='&GEOGRAPHY' \
AREA='&AREA' \
QTR='&QTR' \
WFFMT='EXL2K'), $