Home » SQL & PL/SQL » Client Tools » New Page/Break on commands (SQL *Plus)
New Page/Break on commands [message #280175] Mon, 12 November 2007 12:56 Go to next message
adrianbiccum
Messages: 9
Registered: October 2007
Junior Member
Hi All,

We're trying to format a report where the report breaks on a new page, physically, when a column has a new value...

We set the Newpage to 0, but it always prints a blank page before the report and in between all the pages until it gets to the new column value then it prints to a new page.

Has anyone ever run into this? How did resolve it?

Thanks!

AB
Re: New Page/Break on commands [message #280177 is a reply to message #280175] Mon, 12 November 2007 13:03 Go to previous messageGo to next message
Michel Cadot
Messages: 64103
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Break on <column> skip page

Regards
Michel
Re: New Page/Break on commands [message #280181 is a reply to message #280175] Mon, 12 November 2007 13:32 Go to previous messageGo to next message
adrianbiccum
Messages: 9
Registered: October 2007
Junior Member
Sorry, I should have specified that we already have that line in our report...

Break on <column> skip page

It's working to a degree, what we'd like to get rid of are those extra blank pages we're getting when we run the report.

??

Thanks AB
Re: New Page/Break on commands [message #280183 is a reply to message #280181] Mon, 12 November 2007 13:46 Go to previous messageGo to next message
Michel Cadot
Messages: 64103
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Maybe you just can't avoid of them.
Use an extra and external program (like sed) to get rid of them.

Regards
Michel
Re: New Page/Break on commands [message #280228 is a reply to message #280183] Mon, 12 November 2007 20:03 Go to previous message
rleishman
Messages: 3724
Registered: October 2005
Location: Melbourne, Australia
Senior Member
You can't avoid the first one, but setting
SET PAGESIZE 50000
or
SET PAGESIZE 0
will help with the intermediate breaks.

Note that you never get intermediate page breaks with PAGESIZE 0, but nor do you get column headings.

Ross Leishman
Previous Topic: SP2-0311: string expected but not found
Next Topic: SQL*PLUS generated abnormal file size.
Goto Forum:
  


Current Time: Sun Dec 04 02:31:05 CST 2016

Total time taken to generate the page: 0.21515 seconds