Access 2003 - Adding a field to an existing report and filtering d

[Guest]

We have a database in our office that contains multiple tables, which are
linked in various fashions.

A report has been generated which includes a person's name, which department
they are employed by, and their start date (this information is being pulled
from a Table entitled "Personal"). I need to add a field from another table.
I know how to do this, however, when I add this field from the other table,
the names for EVERYONE shows up. I only want to have names for people in the
ONE department in this report. How do I filter the information to show only
the names, the one department, the start date, and the new added field?

I do not believe this report was based on a query, it was based directly on
the information from the table.

Should this report be based on a query, or is there a way to revise the
existing report?

Any assistance would be greatly appreciated.

Brenda

 

[Marshall Barton]

We have a database in our office that contains multiple tables, which are
linked in various fashions.

A report has been generated which includes a person's name, which department
they are employed by, and their start date (this information is being pulled
from a Table entitled "Personal"). I need to add a field from another table.
I know how to do this, however, when I add this field from the other table,
the names for EVERYONE shows up. I only want to have names for people in the
ONE department in this report. How do I filter the information to show only
the names, the one department, the start date, and the new added field?

I do not believe this report was based on a query, it was based directly on
the information from the table.

Should this report be based on a query, or is there a way to revise the
existing report?

You can not use fields feom two tables without using a query
as the report's record source. Once you determine which
query, check its Join Type to make sure it's appropriate.
If it not immediately obvious, try running the query
directly from the query design window to see what it's
doing.

If you can't find the problem, post back with a Copy/Paste
of the query's SQL statement.