A Quick Report's PL/SQL WHERE clause needs to compare against a literal string containing an ampersand character (e.g. 'Dungeons & Dragons'), but including the literal & causes 'Invalid member name' — how do you actually get a literal ampersand into the comparison?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Build the string using the ASCII/CHR function for the ampersand instead of typing the character literally — for example, WHERE name = 'Dungeons ' || chr(38) || ' Dragons' — since Quick Report's own SQL parser intercepts a literal & anywhere in the statement as a substitution-parameter marker rather than passing it through as a plain character. Concatenating chr(38) in place of the literal & character avoids that interception entirely.

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