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" wrote:

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.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com