Simplest would be to put all their records in to the same table. You can probably design your system to work from a single table that contains records for both types of employees. You can also set up a "report" table soley for your report and import records from your two separate tables whenever you want to produce this report. This can be slow due to the import, but it works.
You can also set up a third table were each record links to exactly one employee from one table or the other. Then base your report layout on this table that serves as the "union" of your two separate tables. This last method is often used to link up two very different sets of data into what appears to be a common table. You can define fields for any data (such as a person's name) in the "union" table and only keep fields that are specific to that one type of employee in the separate related tables.
Thank you very much for your response! It seems your third method works great for my purpose because the two tables I want to combine are very different and I need only to pull data from the only three common fields: date, name, and total. But I am not sure how to design the third table to link to exactly one employee from ONE tabke or the OTHER, without "joining" them into one record. Could you please explain a little more?
I appreciate your help!
Personnel::__pkPersonnelID = Technicians::_fkPersonnelID
Personnel::__pkPersonnelID = Receptionists::_fkPersonnelID
For an explanation of the notation that I am using, see the first post of: Common Forum Relationship and Field Notations Explained
That makes sense. I will try it later. Thanks very much!