Using Queries better for creating Data Entry Forms?

[MStadnik]

I am just setting up a brand new database and am building the forms to be
used for data entry, editing, etc. Since all the fields will be needed on
each form is there any reason to base the form on a query of all the fields
in the table rather than just using the table itself? If so, I notice the
attachment fields have a number of fields associated with them that seem to
clutter up the resulting form - where I don't see all the individual pieces
when I build the form based on the table... Do I need to keep those? If not,
what is the preferred method for modyifying the form fields. Thanks for any
help.

 

[Rick Brandt]

I am just setting up a brand new database and am building the forms
to be used for data entry, editing, etc. Since all the fields will be
needed on each form is there any reason to base the form on a query
of all the fields in the table rather than just using the table
itself? If so, I notice the attachment fields have a number of fields
associated with them that seem to clutter up the resulting form -
where I don't see all the individual pieces when I build the form
based on the table... Do I need to keep those? If not, what is the
preferred method for modyifying the form fields. Thanks for any help.

If you need all of the fields then the only advantage to using a query would
be to impose a more reliable sort order on the records as shown in the form
and/or to have a criteria applied. An example of the latter might be a case
where you don't allow "hard" delettions of records, but rather just set a
flag field in the table to indicate that the record is "voided" or similar.
Your form could then never display "voided" records simply by having that in
the criteria of the underlying query.

Both sorting and filtering can also be done at the form level using a table
as its RecordSource, but the sorting from a query is more reliable (the user
can't accidentally change it) and filtering at the form level could also be
turned off by the user and in some cases that is not wanted. More likely
you might want the user to be able to apply and remove various filters of
his own and if you want some criteria to always be applied then having that
in the query is the most practical way to achieve that.

 

[MStadnik]

Okay... so a Form based on Query looks a bit different and one of the things
(besides the header) is that attachment fields bring over all their "extra"
stuff with them that you don't normally see when you create a form from a
table. Are these extra fields necessary... and if so is there a way to "hide"
them from the user? It creates a very confusing form. Though to be honest,
I'm not inclined to use the query to create the form at this point but I
would like the information in case I later decide to use this approach.
Thanks for your help!

 

[Rick Brandt]

Okay... so a Form based on Query looks a bit different and one of the
things (besides the header) is that attachment fields bring over all
their "extra" stuff with them that you don't normally see when you
create a form from a table. Are these extra fields necessary... and
if so is there a way to "hide" them from the user? It creates a very
confusing form. Though to be honest, I'm not inclined to use the
query to create the form at this point but I would like the
information in case I later decide to use this approach. Thanks for
your help!

Sorry, but attachment fields are new in Access 2007 of which I have little
experience. So far I have only used it to diagnose things in my apps that
don't work in 2007 and for testing.