A Quick Report fails with 'Invalid Member Name' even though the exact same SQL runs perfectly in PL/SQL Developer, and the query includes a couple of UNION ALL statements plus prompts like ('%&User_ID%') that have worked fine in other reports before.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Check for any other ampersand (&) character appearing anywhere in the SELECT list itself, separate from your intended prompt/parameter syntax — Quick Report's own SQL parser treats any & it encounters as a substitution-parameter marker, including inside string literals or expressions within the SELECT clause, not just where you intended a genuine user-input prompt. An unintended & elsewhere in the query (easy to miss in a longer SELECT list with UNION ALL branches) gets misinterpreted as an undefined substitution parameter, producing 'Invalid Member Name' rather than a syntax error, even though Oracle itself would accept the same literal & without complaint.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions