T
Tim Tabor
Is there any way to print the form view with a page break after each record,
without designing a report?
Thank you
without designing a report?
Thank you
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
R
Raghu Prakash
Hi Tim,
Add a page break by using the page break control
In reports, you use a page break control to mark where you want to start a
new page within a section. For example, if you want a report's title page
and introductory message printed on separate pages, place a page break in
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.) after the controls that you want to appear on the
title page and before the controls for the second page.
Open the report 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.).
Click the Page Break tool in the toolbox (toolbox: A set of tools that is
available in Design view to add controls to a form, report, or data access
page. The toolset available in page Design view is different from the
toolset available in form and report Design view.).
Click where you want to place the page break. Place the page break above or
below a control to avoid splitting data in that control.
Microsoft Access marks the page break with a short dotted line on the left
edge of the report.
Notes
If you want each group or record in a report to start on a new page, set
the ForceNewPage property of the group header (group header: Used to place
information, such as group name or group total, at the beginning of a group
of records.), group footer (group footer: Used to place information, such
as group name or group total, at the end of a group of records.), or 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.).
The Catalog report in the Northwind sample database has an example of using
a page break in the report header. To view this report, open the Northwind
database in your Microsoft Office folder's Samples folder, and then open
the Catalog report in Design view.
For Further Information :
http://office.microsoft.com/assistance/preview.aspx?AssetID=HP051873361033&C
TT=4&Origin=CH063650481033
Please let me know has this helped You...
Thank you...
Raghu...
This posting is provided "AS IS" with no warranties, and confers no rights.
Add a page break by using the page break control
In reports, you use a page break control to mark where you want to start a
new page within a section. For example, if you want a report's title page
and introductory message printed on separate pages, place a page break in
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.) after the controls that you want to appear on the
title page and before the controls for the second page.
Open the report 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.).
Click the Page Break tool in the toolbox (toolbox: A set of tools that is
available in Design view to add controls to a form, report, or data access
page. The toolset available in page Design view is different from the
toolset available in form and report Design view.).
Click where you want to place the page break. Place the page break above or
below a control to avoid splitting data in that control.
Microsoft Access marks the page break with a short dotted line on the left
edge of the report.
Notes
If you want each group or record in a report to start on a new page, set
the ForceNewPage property of the group header (group header: Used to place
information, such as group name or group total, at the beginning of a group
of records.), group footer (group footer: Used to place information, such
as group name or group total, at the end of a group of records.), or 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.).
The Catalog report in the Northwind sample database has an example of using
a page break in the report header. To view this report, open the Northwind
database in your Microsoft Office folder's Samples folder, and then open
the Catalog report in Design view.
For Further Information :
http://office.microsoft.com/assistance/preview.aspx?AssetID=HP051873361033&C
TT=4&Origin=CH063650481033
Please let me know has this helped You...
Thank you...
Raghu...
This posting is provided "AS IS" with no warranties, and confers no rights.
E
Ernie
Forms are normally used to view / enter data on screen.
Reports are normally used for printing. Trying to use a
form for printing is trying to put the cart before the
horse.
Reports are normally used for printing. Trying to use a
form for printing is trying to put the cart before the
horse.
T
Tim Tabor
Ernie said:Forms are normally used to view / enter data on screen.
Reports are normally used for printing. Trying to use a
form for printing is trying to put the cart before the
horse.
Dumping data the way it was input can be handy. Thanks, though.
B
Bruce
You don't need to go to much trouble to design a report
from a form. Open the form and save it as a report (File
report.
You can get away with printing a form (rather than a
report) as long as you don't need any of the sorting,
grouping, and other advantages of reports. You can add a
page break to a form, if you insist on printing it. Just
use the toolbox. I find that displaying text etc. for
optimum onscreen viewing uses a very different format from
that used for optimum printing, even if there were no
other advantages to printing reports.
from a form. Open the form and save it as a report (File
command button to the form to either preview or print theSave As). Use the command button wizard to add a
report.
You can get away with printing a form (rather than a
report) as long as you don't need any of the sorting,
grouping, and other advantages of reports. You can add a
page break to a form, if you insist on printing it. Just
use the toolbox. I find that displaying text etc. for
optimum onscreen viewing uses a very different format from
that used for optimum printing, even if there were no
other advantages to printing reports.
T
Tim Tabor
I find that displaying text etc. for
Thank you for the tips about printing a form, Bruce. I must say, however,
I'm puzzled about the strong opinions about printing forms. MS obviously
thinks there's some value in it, or else they wouldn't have provided a print
command for a form view. If I were only using Outlook to develope more or
less complete apps for others I would probably agree. But I use it for *a
lot* of quick and dirty work, and at some stage in the work, just dumping
the data (preferably w/o a form view spanning two pages) is quite helpful.
Sorry if I offended some folks' senses of design and order.
T
optimum onscreen viewing uses a very different format from
that used for optimum printing, even if there were no
other advantages to printing reports.
Thank you for the tips about printing a form, Bruce. I must say, however,
I'm puzzled about the strong opinions about printing forms. MS obviously
thinks there's some value in it, or else they wouldn't have provided a print
command for a form view. If I were only using Outlook to develope more or
less complete apps for others I would probably agree. But I use it for *a
lot* of quick and dirty work, and at some stage in the work, just dumping
the data (preferably w/o a form view spanning two pages) is quite helpful.
Sorry if I offended some folks' senses of design and order.
T
B
Bruce
I tend to be very methoodical and consistent in my
approach to databases. I label every single control, I
use consistent naming conventions, I print reports and use
forms on screen, etc. For me, it has a lot to do with the
look of the thing. I use command buttons, combo boxes,
and other such things on forms that I would not want to
print. I can set command buttons and other items to
appear on screen only, but to me it is easier to just make
a report and eliminate the unnecessary items. Also, as I
mentioned, the best formatting for on screen presentation
is not necessarily the best for printing, especially if
the databases are for general use.
You can print anything you want. If all you need is in
effect a screen shot, you certainly can print a form with
a page break. For me, the formatting, sorting, and
grouping option available on a report make it the object
of choice for printing in almost all cases. For one
thing, it is much easier to hide unused fields on a
report. When it doesn't really matter, I use a report
anyhow. It keeps all of my printable object together.
In a pinch, you can use a wrench to hammer a nail, but I
wouldn't want to undertake a carpentry project using a
wrench in that way. Perhaps the analogy is extreme, but
the point is that the object designed for printing is
usually the best choice for that form of output.
approach to databases. I label every single control, I
use consistent naming conventions, I print reports and use
forms on screen, etc. For me, it has a lot to do with the
look of the thing. I use command buttons, combo boxes,
and other such things on forms that I would not want to
print. I can set command buttons and other items to
appear on screen only, but to me it is easier to just make
a report and eliminate the unnecessary items. Also, as I
mentioned, the best formatting for on screen presentation
is not necessarily the best for printing, especially if
the databases are for general use.
You can print anything you want. If all you need is in
effect a screen shot, you certainly can print a form with
a page break. For me, the formatting, sorting, and
grouping option available on a report make it the object
of choice for printing in almost all cases. For one
thing, it is much easier to hide unused fields on a
report. When it doesn't really matter, I use a report
anyhow. It keeps all of my printable object together.
In a pinch, you can use a wrench to hammer a nail, but I
wouldn't want to undertake a carpentry project using a
wrench in that way. Perhaps the analogy is extreme, but
the point is that the object designed for printing is
usually the best choice for that form of output.