A family of Microsoft relational database management systems designed for ease of use.
You can return the time spent to date over the whole of the query's result table with a query like this:
SELECT Status, [Release Date], Ticket, [Qty Scrap], (Qty Good], Labor, [# of People],
(SELECT SUM(Labor*[# of People])
FROM [Tracking Log Query] AS Q2
WHERE Q2.[Release Date] <= Q1.[Release Date]) AS TimeSpentToDate
FROM [Tracking Log Query] AS Q1
ORDER BY [Release Date];
This would compute the time spent to date in Release Date order, but as your query returns the rows in Ticket order, you might want it to return the running sum of time spent in that order in which case the query would be:
SELECT Status, [Release Date], Ticket, [Qty Scrap], (Qty Good], Labor, [# of People],
(SELECT SUM(Labor*[# of People])
FROM [Tracking Log Query] AS Q2
WHERE Q2.Ticket <= Q1.Ticket) AS TimeSpentToTicket
FROM [Tracking Log Query] AS Q1
ORDER BY Ticket;
However, I would normally have expected a query like yours to include a JobID volume or similar to identify each subset of rows per job, which would enable the subquery to be further correlated with the outer query, and this return the time to date spent per job.
There are other ways to return balances (running sums), examples of which you'll find in Balances.zip in my public databases folder at:
https://1drv.ms/f/c/44cc60d7fea42912/EhIppP7XYMwggESpAAAAAAABaDKZCllSuweYBPJ5zKa3cg
This little demo file illustrates a number of queries to return balances in different contexts.
You might also like to take a look at TimeArithmetic.zip in the same OneDrive folder. This illustrates the use of a number of functions by which arithmetic can be done on values of Date/Time data type rather than hours.