Karen, There was some discussion of something similar a few months back about keeping data together.
I've had a (very) quick look through my stored e-mails but couldn't find the correspondence. I seem to remember that Razzak said that the problem was sorted in v7 but whether that was the same problem you are experiencing I'm not sure. From memory it sounds quite similar. Just a thought, have you tried using zero for the page length (no paging) and output to a file? If so, do you still get the problem? If you do then it's probably a Report Writer problem, if you don't I would suggest it's a data/report definition problem. Regards, Alastair. ----- Original Message ----- From: "tellef" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 19, 2002 11:06 PM Subject: RE: Problem with DOS report > > >Make sure your lookup variables are calculated for the appropriate section > > >of your report. > >Say you have var break_head_1 and it is located in the H1 section of the > >report, you need to be sure that break_head_1 is calculated at the H1 > level > >and not the D level, otherwise you will wind up w/ data from the previous > >row. > > My lookup variable is located and calculated in the DETAIL section, > not the header sections. I have columns, not variables, located in > the header sections so variable definitions aren't a problem. > > >One other thing to check is where the variables are being reset. It > sounds > >like maybee you are resetting variables at the page break level causing > >problems. > > My bad lookup variable is not being reset at all because it's > a client name lookup at the detail level. No need to reset. > > My bad summing variable (the one that ignores that first row) > is located in the F2 section, calculates at Detail level (Sum of....), > and is reset only for the Break2 section. No variables are reset > at the Page level. Thanks for the suggestions, you made me check > all these things just to be sure! > > Remember that all the other pages of this report print just fine. > It is ONLY when a break header is at the bottom of a page and the > first row of data is at the top of the next page that that section > gets messed up. > > > Karen > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
