two relations between same two tables

[Christopher Glaeser]

tblWorkOrders has two fields TakenBy and AssignedTo which are both employees
and are relations to tblEmployees. My forms are working fine, but I'm not
sure how to build a report. The Report Wizard only let's me specify Name of
tblEmployees once, and I'm not clear on how to specify the two links using
the Query Builder (apparently, the Query Builder only specifies the field of
the foreign table, and does not specify the field of the main table, so I'm
not clear on how to specify both fields of the main table). Helpful hints
on how to include two unique employee names in a WorkOrder report would be
greatly appreciated.

Best,
Christopher

 

[Marshall Barton]

tblWorkOrders has two fields TakenBy and AssignedTo which are both employees
and are relations to tblEmployees. My forms are working fine, but I'm not
sure how to build a report. The Report Wizard only let's me specify Name of
tblEmployees once, and I'm not clear on how to specify the two links using
the Query Builder (apparently, the Query Builder only specifies the field of
the foreign table, and does not specify the field of the main table, so I'm
not clear on how to specify both fields of the main table). Helpful hints
on how to include two unique employee names in a WorkOrder report would be
greatly appreciated.

Create the query for the report first. Add the employees
table twice. Join the work orders table to one of the
employees tables from the TakenBy field and Join the other
employees table to the AssignedTo field.

 

[Christopher Glaeser]

Create the query for the report first. Add the employees

table twice. Join the work orders table to one of the
employees tables from the TakenBy field and Join the other
employees table to the AssignedTo field.

Thanks for the quick response. I'll give it a try.

I recently purchased the AppDev Access 2000 training CDs, and if I
understood the chapter on Reports, they suggested creating queries within
the Report rather than basing the Report on another Query. They claimed the
Report query has the same power as a Query. Does using a Query in my
example offer better ease-of-use? Or, are there queries that can not be
done in a Report that require a Query?

Best,
Christopher

 

[Marshall Barton]

Thanks for the quick response. I'll give it a try.

I recently purchased the AppDev Access 2000 training CDs, and if I
understood the chapter on Reports, they suggested creating queries within
the Report rather than basing the Report on another Query. They claimed the
Report query has the same power as a Query. Does using a Query in my
example offer better ease-of-use? Or, are there queries that can not be
done in a Report that require a Query?

It doesn't matter. Creating the query by using the Build
button in the report's RecordSource property is just a
roundabout way of getting to the query designer. I think
it's easier to test the query if you start from the query
designer.

 

[Christopher Glaeser]

I think it's easier to test the query if you start from the query

designer.

OK, that makes sense. I need easier. Thanks again.

Best,
Christopher