shift to the next column as needed?

[ooxx]

Dear anyone,

Can the Access do the shift from printing the first column to the next
column as we needed, in place of its printing to the bottom and continuing
its printing itself?
If we would like to print the records from now on the 21st to the right
side column in order to make the report balance looking, if there are only 40
product names.

Thanks,

 

[Rick B]

Your post is very confusing. What does this mean: "in place of its printing
to the bottom and continuing its printing itself"? And this: "print the
records from now on the 21st to the right side column"?

Please try again. If you are trying to make a two-column report, open the
HELP file and type in "Columns". The first link that popped up for me was
"Create a multiple-column report". This article included the following
instructions...


Create a multiple-column report

1.. Create a report and open it in Design view.
2.. On the File menu, click Page Setup.
3.. In the Page Setup dialog box, click the Columns tab.
4.. Under Grid Settings, in the Number Of Columns box, type the
number of columns you want on each page.
5.. In the Row Spacing box, type the amount of vertical space you
want between each record in the detail section.
Note If you left space between the last control (control: A
graphical user interface object, such as a text box, check box, scroll bar,
or command button, that lets users control the program. You use controls to
display data or choices, perform an action, or make the user interface
easier to read.) in the detail section and the bottom edge of the detail
section, you can leave Row Spacing set to 0.

6.. In the Column Spacing box, type the amount of space you want
between the columns.
7.. Under Column Size, type the width you want for a column in the
Width box. You can set the height of the detail section by typing a number
in the Height box or by adjusting the height of the section in Design view
(Design view: A window that shows the design of these database objects:
tables, queries, forms, reports, macros, and data access pages. In Design
view, you can create new database objects and modify the design of existing
ones.).
8.. Under Column Layout, click Down, Then Across or Across, Then
Down.
9.. Click the Page tab.
10.. Under Orientation, click Portrait or Landscape.
Notes

a.. When a multiple-column report is printed, the report header
(report header: A report section that is used to place information (such as
a title, date, or report introduction) at the beginning of a report.) and
footer (report footer: A report section that is used to place information
that normally appears at the bottom of the page, such as page numbers,
dates, and sums.) and page header (page header: Used to display a title,
column headings, dates, or page numbers at the top of every page in a form
or report. In a form, the page header appears only when you print the form.)
and footer (page footer: Used to display page summaries, dates, or page
numbers at the bottom of every page in a form or report. In a form, the page
footer appears only when you print the form.) span the full width of the
report, but the group header (group header: Used to place information, such
as group name or group total, at the beginning of a group of records.) and
footer (group footer: Used to place information, such as group name or group
total, at the end of a group of records.) and detail section (detail
section: Used to contain the main body of a form or report. This section
usually contains controls bound to the fields in the record source but can
also contain unbound controls, such as labels that identify a field's
contents.) of a multiple-column report span the width of one column.

b.. The Products by Category report in the Northwind sample database
displays data in multiple columns. To view this report, open the Northwind
database in the Samples subfolder of your Office folder, and then open the
Products by Category report in Design view.

 

[ooxx]

Thanks for help but the records wil be full of one side column while
the right side column is blank. I have the column layout 'down then across'
property. That is if I have the records of only 40 records, the layout will
print only on left till blank. So, to do is to make the look in a little
adjustment to print the same on the right side by dividing, half left and
half right to have the records printed.

Thanks,

 

[Marshall Barton]

Thanks for help but the records wil be full of one side column while
the right side column is blank. I have the column layout 'down then across'
property. That is if I have the records of only 40 records, the layout will
print only on left till blank. So, to do is to make the look in a little
adjustment to print the same on the right side by dividing, half left and
half right to have the records printed.

It sounds like you are doing this in a subreport where you
should be using Across then Down.

Because the main report is in charge of Page issues,
subreport are unaware of page boundaries. Down then Across
only works in subreports with their Can Grow property set to
No.

 

[ooxx]

Thanks,

Something is that when I have created a sub-report report, and I made the
property 'can grow' to 'No', it printed as you suggested. But when there
are more than one categories of the products, it printed non of the rest of
them.

It is about the flexibility to have other categories to be printed as well,
if to have the property of 'can grow' to 'No' this way, the rest of the
categories won't let out.
Is there any other possible?

Thanks,

 

[Marshall Barton]

With CanGrow set to Yes, you should use Across then Down.

If that makes a hash of your data, you can try to figure out
a calculation in the report's record source query that adds
a field so the report can sort the records in such a way
that Across then Down arranges the data to look as if it
were down then across. This is not really practical if you
are grouping on other fields and want groups to start a new
column. If you try to pursue this unwieldy approach, you'll
have to play around with the calculation, the grouping and
who knows what else.

In some limited situations, you might be able to use a
separate subreport for each column, but again it gets
ridiculously messy if you are using more than two groups.

Bottom line: There are no good work arounds for the general
problem. If there is a work around for your situation, it
will depend on what you are trying to do in your specific
report.