C
Chris
I have a database that records transactional information of downtime by reason code for production lines in our company
I have created a report that creates a Paredo chart (sorted bar chart) of these transactions filterable by date range
This report had to report each production line on a separate page, with a bar chart of sorted (descending) minutes dow
for that Production line
Unfortunately, sometimes (not always but VERY frequently, go figure why) One production line's chart will be repeated on the next production line's page. The two charts are identical, but when I look at the underlying query, the data is all different
This required a macro, here's how it was done
Step 1: Run a make-table query to gather the date-ranged transactional data, based on start/end date parameters and summarize that data by production line and reason code. (Minutes Down is summarized
Step 2: Run a report based on a query of the made table, sorted in descending sequence by summarized minutes down for the date range
Step 3: Cuss when it doesn't work as expected
The report is designed over the 'production lines' table, with an embedded chart (vertical bar) over the query "SumforAnalysisSorted". I get an error when I try to use the Master/Child Link fields but I have a relationship set up between the two, the master (Production Lines) has a primary key, and so I just key in the linking fields, Productionline and it accepts them, as the Microsoft Knowledgebase suggested.
When I manually run the first query (The make-table) and the second query, I get data, sorted by the summarized minutes down, and it's not duplicated. But when I run the report, I get line 7's chart on lines 7 & 8 and line 9 is ok. Or sometimes if it's feeling cranky, line 8 & 9 are identical and line 7 is the loner
Help! (pleeze!) :-
I have created a report that creates a Paredo chart (sorted bar chart) of these transactions filterable by date range
This report had to report each production line on a separate page, with a bar chart of sorted (descending) minutes dow
for that Production line
Unfortunately, sometimes (not always but VERY frequently, go figure why) One production line's chart will be repeated on the next production line's page. The two charts are identical, but when I look at the underlying query, the data is all different
This required a macro, here's how it was done
Step 1: Run a make-table query to gather the date-ranged transactional data, based on start/end date parameters and summarize that data by production line and reason code. (Minutes Down is summarized
Step 2: Run a report based on a query of the made table, sorted in descending sequence by summarized minutes down for the date range
Step 3: Cuss when it doesn't work as expected
The report is designed over the 'production lines' table, with an embedded chart (vertical bar) over the query "SumforAnalysisSorted". I get an error when I try to use the Master/Child Link fields but I have a relationship set up between the two, the master (Production Lines) has a primary key, and so I just key in the linking fields, Productionline and it accepts them, as the Microsoft Knowledgebase suggested.
When I manually run the first query (The make-table) and the second query, I get data, sorted by the summarized minutes down, and it's not duplicated. But when I run the report, I get line 7's chart on lines 7 & 8 and line 9 is ok. Or sometimes if it's feeling cranky, line 8 & 9 are identical and line 7 is the loner
Help! (pleeze!) :-