precisonline
President/Chief Technologist
Administrator
Rock Star
    
Posts: 1532
|
 |
« Reply #15 on: August 04, 2009, 11:27:39 AM » |
|
Okay. This is pretty much what I expected, which is... There shouldn't be a break here but SB+ is doing a break because in comparing the last record's value to the current record's value, it sensed that the S.SHIPTRN.KEY changed. "But," you argue, "that information is not in the record, it's in the key!" and of course you would be correct. The problem is that sometimes SB+ gets goofy when breaking on derived values that are based on the key to the record.
There is one thing you could try, but I can't say definitively it'll work. In the derived value for the field S.SHIPTRN.KEY change:
(<0>"G1*2")
...to...
(@KEY"G1*2")
...and see if that produces anything different.
|
|
|
|
|
Logged
|
-Kevin Accidents "happen"; success, however, is planned and executed.
|
|
|
|
adewitt
|
 |
« Reply #16 on: August 04, 2009, 11:40:33 AM » |
|
Would you believe....no change 
|
|
|
|
|
Logged
|
|
|
|
precisonline
President/Chief Technologist
Administrator
Rock Star
    
Posts: 1532
|
 |
« Reply #17 on: August 04, 2009, 11:45:10 AM » |
|
One more thing before I completely give up on this plan... Bring up the report, press F6 and <cr> all the way through, and try again. Likely will have no impact at all, but... allow me my insanity?
|
|
|
|
|
Logged
|
-Kevin Accidents "happen"; success, however, is planned and executed.
|
|
|
|
Tom Pellitieri
|
 |
« Reply #18 on: August 04, 2009, 11:48:36 AM » |
|
Just an extra note here... does the report have a Grand Total section? I've noticed that reports can get a bit weird with breaks when there's Break lines but no Grand Total lines.
--Tom
|
|
|
|
|
Logged
|
|
|
|
|
adewitt
|
 |
« Reply #19 on: August 04, 2009, 12:07:44 PM » |
|
Kevin, I went so far as removing the S.SHIPTRNKEY, filing the report, reopening the report, adding the field and re-filed the report. Nothing.
Tom, it had a Grand Total section, lost it in one of the many iterations and I just readded it.
No change.
|
|
|
|
|
Logged
|
|
|
|
precisonline
President/Chief Technologist
Administrator
Rock Star
    
Posts: 1532
|
 |
« Reply #20 on: August 04, 2009, 12:21:27 PM » |
|
If that information cannot be found in any other attribute of the record you may be in that grey area where you have to reformat what you need into a work file and then report out of the work file.
|
|
|
|
|
Logged
|
-Kevin Accidents "happen"; success, however, is planned and executed.
|
|
|
|
adewitt
|
 |
« Reply #21 on: September 11, 2009, 09:53:11 AM » |
|
After a hiatus I'm back on this little project:  Can someone tell me what's the difference between: Process At End Process Before Exec Process After Exec The hoops System Builder makes you go through to suppress totals (and page breaks) is enough to drive me bonkers. 
|
|
|
|
|
Logged
|
|
|
|
precisonline
President/Chief Technologist
Administrator
Rock Star
    
Posts: 1532
|
 |
« Reply #22 on: September 11, 2009, 11:19:46 AM » |
|
I just did a quick little /RD that showed the sequence is like this:
a) Select criteria is evaluated b) Report prompts for Screen/Print/Aux/... or calls Output Redirection process (F6-F6) c) Process At Start is executed d) Printing Parameters (printer, stationery, options, etc.) are set e) Process Before Execution is executed f) Printer is enabled if appropriate g) Records are selected or ReadNext ID/Next ID and Record process is executed (not sure which process takes precedence if both are filled in) h) Process After Read is executed for each record h1) Process Before Break is executed before each break, regardless of level h2) Process After Break is executed after each break, regardless of level i) At end of report, Process At End is executed j) Spooler file is closed (i.e. PRINTER CLOSE) k) Process After Execution is run.
So to answer your question, the difference between Process At End and Process After Execution is that the former is before the spooler file is closed and the latter is after. It does seem odd that the Proc At Start is first and the Proc After Execution is last, but hey, I only work here...
|
|
|
|
|
Logged
|
-Kevin Accidents "happen"; success, however, is planned and executed.
|
|
|
|