StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9921038
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-03-29T07:39:57.953
FavoriteCount
0
LastActivityDate
2012-03-29T07:39:57.953
LastEditDate
LastEditorUserId
0
OwnerUserId
3811
ParentId
9875535
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
It's highly possible that your original query is slow because of the use of sub-SELECT queries in the WHERE clause that may be executed for each record in your <code>Sort</code> table. If I where you, I would use VBA to reduce each <code>SELECT TOP 1</code> to the single value they are checking, and then re-inject that into the main query. <pre><code>Public Function GetMessyQuerySQL() As String ' First, extract our where-clause data SortDate, SortShift, and ID' Dim sql As String sql = sql & "SELECT TOP 1 sortdate, sortshift, id " sql = sql & "FROM Sort " sql = sql & "WHERE (OccurrenceID = OccurrenceID) " sql = sql & " AND (Sort.repaired <> 0) " sql = sql & " OR (Sort.scrapped<>0) " sql = sql & "ORDER BY sortdate DESC, " sql = sql & " sortshift DESC, " sql = sql & " id DESC;" Dim SortDate as Variant, SortShift As Variant, ID as Variant ' We assume there is always a valid data return by that query! ' Set rs = CurrentDb().OpenRecordset(sql, dbOpenForwardOnly) ' Convert dates to litteral dates in the format #29/03/2012# ' SortDate = Format(rs(0), "\#mm\/dd\/yyyy\#") SortShift = Format(rs(1), "\#mm\/dd\/yyyy\#") SortID = rs(2) rs.Close Set rs = Nothing ' Now, modify the main query with our data from the first ' sql = vbNullString sql = sql & "SELECT OccurrenceID, " sql = sql & " SUM(Sorted) AS SumOfSorted " sql = sql & "FROM Sort " sql = sql & "WHERE (SortDate > %SortDate) " sql = sql & " OR ((SortDate >= %SortDate) " sql = sql & " AND (SortShift > %SortShift)) " sql = sql & " OR ((SortDate = %SortDate) " sql = sql & " AND (SortShift = %SortShift) " sql = sql & " AND (ID > %SortID)) " sql = sql & "GROUP BY OccurrenceID; " ' Replace the %xxx% by their proper values ' sql = Replace(sql, "%SortDate", SortDate) sql = Replace(sql, "%SortShift", SortShift) sql = Replace(sql, "%SortID", SortID) ' Just return the constructed SQL ' GetMessyQuerySQL = SQL End Sub </code></pre> So calling this function would get you SQL code like that: <pre><code>SELECT OccurrenceID, SUM(Sorted) AS SumOfSorted FROM Sort WHERE (SortDate > #17/02/2012#) OR ((SortDate >= #17/02/2012#) AND (SortShift > #29/03/2012#)) OR ((SortDate = #17/02/2012#) AND (SortShift = #29/03/2012#) AND (ID > 25)) GROUP BY OccurrenceID; </code></pre> Anyway that's just the basic principle, you can take it further and if your query is bound to a datasheet form for instance, you can do something like that in the Open event of the form: <pre><code>Private Sub Form_Load() Me.RecordSource = GetMessySQL() End Sub </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSum all records after last no good
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRenaud Bompuis
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. COThe problem I see with this is that it would use the same hard coded dates for every OccurrenceID. I need to find the most recent entry in the Sort table that has either scrapped or repaired parts for each OccurrenceID. Then I need to sum the number of parts sorted after the last defect was found for each OccurrenceID.
 singulars
 PostPostId
 PO
 UserUserId
 USAdmSteck
2. COOops, in my desire/haste to simplify things I missed that the subqueries were related to the main one. Guess I'll have to think of another solution...
 singulars
 PostPostId
 PO
 UserUserId
 USRenaud Bompuis

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.