We have a report that we have enabled olap *tabbed* on. When a user goes to sort it or unhide a column (do anything at all in OLAP actually) they get an error of

0 ERROR AT OR NEAR LINE 198 IN PROCEDURE ADHOCRQ FOCEXEC *
(FOC262) UNBALANCED PARENTHESES
(FOC009) INCOMPLETE REQUEST STATEMENT
BYPASSING TO END OF COMMAND

there's nothing special about line 198. It's just a BY encased in some DM code.

Additionally, we have
-SET TRACEON=ALL;
-SET TRACEUSER=ON;
-SET &ECHO=ALL;
-SET &ECHO=ON;
at the top of this fex, but it doesn't echo the code like usual. We're guessing that this has something to do with OLAP.

Thanks!

Jason

The times I came across this error was with a COMPUTE in the OLAP code.

Is this the case?

Alan, YES!

actually here's of the fact (SUM) fields, we have 17 of the 20 that are COMPUTES.

Is there any way to have the computes without this error?

This message has been edited. Last edited by: Jason K.,

This is one of a few known(!) issue with OLAP COMPUTES, that may be the issue.

If the final parenthesis is just prior to the semi colon, it is removed by the OLAP parser.

So COMPUTE X/F4 = 100*(3+4); would fail, but
COMPUTE X/F4 = (100*(3+4))*1; should work.

The other main issues are a -ve sign causing issues (though not all the time) in a logic based COMPUTE, and that a COMPUTE can only use EQ or NE in a logic expression. Both of these have WARs also.

On a positive note we have had over 500 complex COMPUTES in an OLAP without error with the WARs in place. (The 'we' includes John Gray, Jim Fraser and Manuel Gonzales who all contributed to getting this to work).

I did not know that.
thanks!