A field for each activity is not normalized data structure. Cannot get the graph you want with this table structure. Should be like:
Tech |
Act |
Hrs |
Date |
Shift |
Crew |
1 |
A |
4 |
7/15/2014 |
1 |
1 |
1 |
B |
5 |
7/15/2014 |
1 |
1 |
1 |
C |
3 |
7/15/2014 |
1 |
1 |
1 |
D |
6 |
7/16/2014 |
1 |
2 |
1 |
E |
2 |
7/17/2014 |
1 |
1 |
2 |
A |
4 |
7/15/2014 |
1 |
1 |
2 |
B |
7 |
7/16/2014 |
1 |
3 |
2 |
C |
3 |
7/16/2014 |
2 |
1 |
2 |
D |
2 |
7/17/2014 |
1 |
1 |
It is possible to manipulate the data to a normalized structure with UNION query then use the UNION as source for graphing. UNION must be typed or copy/paste in SQL View of query builder. For some reason, I cannot type UNION in the example query. Replace ______ with UNION.
SELECT ID, [Technician Name] AS Tech, [Date], Crew, Shift, "A1L1" As Act, [A1 L1] AS Hrs FROM Table1
______ SELECT ID, [Technician Name], [Date], Crew, Shift, "A1L2", [A1L2] FROM Table1
______ SELECT ID, [Technician Name], [Date], Crew, Shift, "A1L3", [A1L3] FROM Table1;
Pie graph RowSource:
SELECT UnionT1.Act, Sum(UnionT1.Hrs) AS SumOfHrs FROM UnionT1 WHERE (((UnionT1.Tech)=[Forms]![Par-Pak final].[Technician Name])) GROUP BY UnionT1.Tech, UnionT1.Act;
Correction. If you want bar chart then your table can work. (A normalized structure would actually require a CROSSTAB query for bar graph. Applying filter criteria in CROSSTAB is different from other queries.) The graph RowSource would be like:
SELECT [Date], [A1 L1], A1L2, A1L3 FROM Table1 WHERE ((([Technician Name])=[Forms]![Par-Pak final].[Technician Name]));
Date is a reserved word. Should not use reserved words as field names. Also, should avoid spaces and special characters/punctuation (underscore is exception) in naming convention. Note the space in [A1 L1].