Just to put this one out there since I don't think there's anything on Focal Point about this one already.

I had created a report which builds two hold files, then joins them together for the final output.

The first hold file refers to some amper variables for filtering, and contains the FIND statements for them. The second hold file also uses these variables for filtering.

However, executing this fex, when I was selecting anything other than foc_none for the parameter, I always got FOC262.

Troubeshooting steps:
1. Created a vbscript to check for unbalanced parentheses - none found.
2. It was suggested that an AND might be too close to the bracket, ie AND(stuff..). Not found.
3. It was suggested that a WHERE line was too long, so I broke it up into pieces - no go.
4. It was suggested to try .QUOTEDSTRING on the FIND statement for the amper variable - no go.


After plenty of poking around, I finally got it.

Although I had used Report Painter to create the WHERE statement, it had put single quotes around the amper variables, and I'm not sure why.

So Report Painter had put:
WHERE J6.EMPLOYMENT.SUPERVISOREMPLOYEENUMBER EQ '&SUPERVISOREMPLOYEENUMBER';
and the correct syntax would be
WHERE J6.EMPLOYMENT.SUPERVISOREMPLOYEENUMBER EQ &SUPERVISOREMPLOYEENUMBER;

Just in case anyone happens upon this one, or for myself to find when this one strikes again...

Keith

Keith, does the variable &SUPERVISOREMPLOYEENUMBER is a multiselect one ?

If so, Composer (Layout) provide the variable values with the proper inclosed quotes so you don't need it in the WHERE clause of the fex (must be removed as you did).

Report Painter cannot know if the variable is a multi select or not, so it always put quotes.