This is due to a bug fix within Toad and is intended functionality. In previous versions of Toad, certain non-alphanumeric ASCII characters (e.g. those lower than 0x20h or CHR(32)) that were referenced in scripts caused errors to be displayed when executed within Toad; however, those scripts worked correctly within SQL*Plus and displayed a non-printable character symbol where used. For example, consider the following script:
select '1' from dual;
select chr(27) from dual;
select '2' from dual;
When executed in Toad 13.1 and earlier, an error would be displayed about an invalid character being found in text content; however, executing this through SQL*Plus displayed the following:
The actual character is what's attempting to be displayed even though SQL*Plus and Toad render the character slightly differently. Unfortunately, there's not currently a way to turn this option off as it was intended to make sure Toad behaved like SQL*Plus.
Thanks for the explanation but I've got to say that showing the characters really makes the output look ugly! Also, I tried SQLPlus in unix and I don't see the characters - it behaves exactly as I would like - a form feed acting like a form feed. It only seems to show them when using SQLPlus in Windows.