Re: Sliding and page breaks

On 2007-08-01 15:54:33 -0500, Helpful Harry <helpful_harry@xxxxxxxxxxxxxxxx> said:

In article <2007080114044516807-dougcpa@maccom>, Doug Anderson
<dougcpa@xxxxxxx> wrote:

On 2007-07-30 16:11:47 -0500, Helpful Harry
<helpful_harry@xxxxxxxxxxxxxxxx> said:

In article <2007073009474475249-dougcpa@maccom>, Doug Anderson
<dougcpa@xxxxxxx> wrote:

I've got a layout that is working nearly perfectly. All the sliding is
working as expected, but I still have one nagging formatting problem.

My layout will always be two pages long, depending on a portal on the
first page

NEVER print Portals. Portals are designed for on-screen use, not for
printing.

If you think you need to print a Portal, then you should really be
printing from the related file / table instead (you can use a
Relationship back to the main file / table to obtain any necessary
individual fields from there).

I guess the question I would have in response to this is how do you get
a report to display all the data from a related table. I have table1
with one entry per record, but in table2 I have multiple records for
each entry in table1. When I just put the fields on the fields it
simply pulls the first match in table2 instead of showing all the
related rows. If I use a portal it shows every related record on the
one page of my report that I wanted.

This sounds like a 1<->Many relationship (ie. single records in Table1
are related to many records in Table2). That means you can easily print
the report from Table2, using a normal Body part for the many records
and a relationship link back to Table1 to obtain that single record's
data.

If instead you're using a Many<->Many relationship (ie. many records in
Table1 each related to many records in Table2), then you have to script
the combining of the records from one table into a single field in the
other. Which table you choose will depend on how many records, how
complicated the data, etc. Obvious you choose to print from the more
complicated table, making the combining script easier and quicker.


Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)

So is my problem possibly that I have data from Table1 in the Body along with the data from Table2? Are you saying that I should put the information in Table1 in a header or leading header?

Otherwise I was thinking along the lines of your 2nd suggestion of using some calcs to consolidate the data down to a smaller number of tables used in the layout.

.

Relevant Pages

  • Re: How to do two way lookup for more than 400 row & Coulmn?
    ... format it's display false. ... pls tell me where I am wrong or i have to change the layout. ...
    (microsoft.public.excel.worksheet.functions)
  • Re: Tricky Visual Basic Code help...
    ... moves the current record into a new record in table2. ... this with a little VBA code and a couple custom queries. ... Set a "pushFlag" column in the record in table1 to a specific ... If a duplicate is not found, ...
    (microsoft.public.access.formscoding)
  • Re: Help needed with importing XML
    ... You could add a gratuitous identity column to #temp and use ... Those examples showed how to decompose arbitrary XML in multiple ... table1 and table2. ... But there has to be something in the relational schema tying table1 ...
    (microsoft.public.sqlserver.xml)
  • Re: 2 column pulldown
    ... Allen Browne - Microsoft MVP. ... these field heading names come from Table2 since it is a lookup and so ... Table1 of course only has a single column name ... fieldX from Table1 is pulldown revealing candidate values of Table2. ...
    (microsoft.public.access.forms)
  • RE: Matching Type Query
    ... Table2 as the One side and Table 1 as the Many side? ... Do a Compact & Repair. ... compare every record in Table1 to each record in Table2 ...
    (microsoft.public.access.queries)