Another question

Comments

• gordk St.Catherines On. Canada.

  November 2004 edited 7:18PM

  Hi
  you have to track wether or not you have finished all the details for the current master record and which page you are on
  so you will probably have to add detail footerscould be none visible, and a 2 variables
  1 boolean to track if all done, 1 integer to track pagenumber
  in obp of repeated header check where you are and turn visibility of a child band attached to the header with duplicate memos matching the masterdb
  one way
  another is to look at the mddrelation not neccessarily as the way constructed
  but as to how to connect them to suit
  ie cust master
  orders detail
  items detail
  if you have the necessar fields available in (cust ,orders) (orders,items)
  you can set the table connections up as
  orders master
  items detail
  cust detail
  and put all cust stuff in pg header, since pag header does not move on data
  as long as the orders master rec is not done the pg header will contain correct info
  
  another add detail headers put duplicate memos of mr in detail header
  and control visibilty in dethead obp. or attach the child to obp
  
  
  
• user3997

  November 2004 edited 7:18PM

  Thanks
  
  I finally found a way, much like you said in the last possible way
  you listed: put the master memos in the header of the detail header,
  above the column headings.
  

  ---

  DETAIL HEADER

  ---

  MasterInfo MasterInfo
  ============ (Shading)========
  Detail Header
  ===========================

  ---

  
  ( I'll still have to figure out on a M-D-D-D way of carrying on,
  I have up to 5 levels to figure MDDDD without getting too
  difficult or deep in calculations)
  
  
  Steve Fields
• gordk St.Catherines On. Canada.

  November 2004 edited 7:18PM

  There are other possibilities
  run an ordered by query to group the data to fake a mdddd relation in the outer footer oap reset the boolean var
  or use a column header it will show on every page after pg header
  
• gordk St.Catherines On. Canada.

  November 2004 edited 7:18PM

  hi Syeve here is simplest way
  columheader with fields from master
  groupheader not visible condition value of mdb keyfield
  mdb
  detb
  subdetb
  groupfooterb non visible
  
  code just connect the band events
  var
  done: boolean;
  procedure ColumnHeader1OnBeforePrint(Sender: TfrxComponent);
  begin
  ColumnHeader1.visible := done = false;
  end;
  
  procedure MasterData1OnBeforePrint(Sender: TfrxComponent);
  begin
  done := false;
  end;
  
  
  
  procedure Page1OnBeforePrint(Sender: TfrxComponent);
  begin
  done := true;
  end;
  
  begin
  done := true;// fires at report start
  end.