Why use Form Headers and Footers? Seems like you can do the same on the body of the form

Why use the form headers and footers.  You can enter any data pertinent to data input right on the entry screen where fields are located.  Or am I missing something.
Who is Participating?
Rey Obrero (Capricorn1)Connect With a Mentor Commented:
the form headers and footers can be used to hide/unhide controls in one command line ( this is just one of the simple usage)

if you don't need them, just don't use them
Dale FyeConnect With a Mentor Commented:
They are great for controls which are not bound to the current record, or for continuous forms.

I generally put search and filter controls and buttons for a wide variety of actions in the forms header.

I use the footer for custom navigation buttons, Save, Cancel, Close buttons and in continuous forms to display sums or counts of numeric fields in the continuous portion of the form.
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

Nick67Connect With a Mentor Commented:
Ditto what @fyed said.
Construction of data entry forms is a bit of an art form
<You can enter any data pertinent to data input right on the entry screen where fields are located>

I don't permit that.  Editing, yes -- Entry, no.
That way I can control when new records get created, and ensure that the data is all valid.
I do that through unbound controls and a command button in the form header
The form detail is where the continuous mass of editable records gets displayed.

Simple forms don't generally use the header/footer much.
Go ahead and use the form wizard to create a tabular (continuous) form
All the column labels go in the header.

Most folks don't use datasheet forms.
It's too easy for the end-users to hose the data up accidentally
Jim Dettman (Microsoft MVP/ EE MVE)Connect With a Mentor President / OwnerCommented:

  The main reason for placing controls in a header or footer is that they won't scroll off.

Bill RossConnect With a Mentor Commented:

If you place a button like "Exit" for example a the bottom of the form footer it will always be in the same place.  This is especially useful for continuopus forms.  You can also accent the data by setting the detail background to one color and the form header/footer to another.

Jeffrey CoachmanConnect With a Mentor MIS LiasonCommented:
Not much to add to what the other great experts posted here.

But a little history may be in order.

Reports and Forms evolved concurrently so some things that are more useful in reports ended up in Forms and vice versa.

With every new version of Access the line between Forms and Reports get blurred a little more...

For example, in Access versions previous to 2007, reports had no "Interaction".
Now they do have a bit: ...In Report view you can Filter, click buttons and activate hyperlinks

Nick67Connect With a Mentor Commented:
Ditto what @boag2000 said.

You shouldn't print forms.  Others do disagree with my doctrinairie stance on that.
I insist that reports are for printing, not forms.  Nevertheless...
If you print a form, the form header and footer behave like the report header and footer do--Printing once at the very beginning (header) and once at the very end (footer)
You can also turn on a page header and footer for forms.
They do not have the same events that reports sections do, however.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.