Hi David...a "newpage=no" is never generated by the painter and so one just needs to be careful when trying to change the setting by regenerating the DW...but this is a great suggestion nonetheless. By default, it will either have "newpage=yes" or nothing at all, depending on whether the checkbox is checked at design time. It will still accept "newpage=no" (no errors will be generated) if this was inserted prior to regeneration and will turn the newpage setting off.

So, the point being that if the datawindow object is initially created with the setting off and then one attempts to change it to on dynamically by looking for the position of "newpage=no" it won't find it...you'll have to insert the entire "newpage=yes" in the correct position.

Good point, so design with it on first :)

Agreed ;)

Thanks, I will try that.

Might be tricky if you are still wanting the group break, just no page break. But this does seem a reasonable solution.

just have 2 groups setup to handle it. we use a generic object that runs any report and is setup at runtime, and it includes option to change compute fields, so that is why i use this technique to allow the user to decide at runtime whether to have the page break or not. It is incredibly useful.



if i used a window for that specific report, i would probably just change the group by syntax at runtime.



In any case, it is a shame that it isn't changeable directly via modify. it really seems like a stupidly easy thing to do.