StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18227936
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-14T09:28:55.103
FavoriteCount
0
LastActivityDate
2013-08-14T09:28:55.103
LastEditDate
LastEditorUserId
0
OwnerUserId
2478298
ParentId
10036758
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
The UNION query is intended to be used when you want to retrieve data from different tables but with the same structure. In your situation, I think the best solution is a JOIN query, like <pre><code>SELECT M.field1, M.field2, M.field3, H.field1, H.field2 ...whatever fields you need FROM Managers as M LEFT OUTER JOIN [Design Hours Table] as H ON H.Person = M.PersonID ORDER BY ... whatever order you want </code></pre> You can use this query as RowSource for a report, telling Access to group the results by all the fields in the Managers table. But if you are using that for a form, then you can use a Form/Subform combination. You set your original query as the RowSource of the form, and design it with all the desired fields and labels. Then you insert a SubForm, <img src="https://i.stack.imgur.com/51yHJ.png" alt="Adding a Subform"> and tell Access to use an existent table or query for the subform data, then choose the Design Hours table for that, and select to show records in Design Hours for each record in Managers using the field PersonID. Now, there is another issue I wanted to comment: You have a PersonID field in the Managers table, which is correct, since a manager IS A person. What is incorrect in your design is the existence of a FirstName and LastName columns in the Managers table (unless it is not really a table, but a query). The reason is that the PersonID defines a set of properties, FirstName and LastName being among them. So, with your design, you could end up with a manager having PersonID = 2013, FirstName = John, LastName = O'Connor and the ID 2013 in the People table referring to FirstName = Peter, LastName = Sellers, which would be an inconsistency. Also, you don't need an ID in this table, since the field PersonID is best fitted to serve as PK for this table. You retrieve the Name and SurName from the People table, so the join would be something like <pre><code>SELECT M.field1, M.field2, M.field3, P.FirstName, P.LastName, H.field1, H.field2 ...whatever fields you need FROM (Managers as M INNER JOIN People as P ON P.ID = M.PersonID) LEFT OUTER JOIN [Design Hours Table] as H ON H.Person = M.PersonID ORDER BY ... whatever order you want </code></pre> Regards,
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMS-Access 2003: how to combine query criteria that depend on different tables
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USClon
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.