For Any Use & On Any Platform
Contextual Guidance at the moment of need helps your employees/users adopt software o& achieve even the most complex tasks instantly. Boost knowledge retention, software adoption & employee engagement with easy solution.
Course Of The Month
8 days, 9 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
I Would Like my Count Field Query to Return Zeroes for Dates With No Data Instead of Simply Not Listing That Date
Posted on 2011-09-30
I seem to have a continuous problem with this. I have a table with ALL possible dates (They are actually all Week Ending Saturday Dates.)
I have another table with actual data and the Week Ending Saturday Date associated with that piece of data.
My query is a joining query that uses ALL of the possible dates. However it does not seem to be doing that. There are weeks missing. I have my SQL below
I have another table with actual data and the Week Ending Saturday Date associated with that piece of data.
My query is a joining query that uses ALL of the possible dates. However it does not seem to be doing that. There are weeks missing. I have my SQL below
SELECT Count(NZ(B_ClosedByWeek_CARs_Tbl.CAR_Num_Full,0)) AS Closed, CAR_Possible_WEDATES_W_Leaps_tbl.PossibleWeekEndingDates AS Week INTO C3_ClosedbyWeek_KOJ_Time_Line_Count_tbl
FROM B_ClosedByWeek_CARs_Tbl RIGHT JOIN CAR_Possible_WEDATES_W_Leaps_tbl ON B_ClosedByWeek_CARs_Tbl.WEDate = CAR_Possible_WEDATES_W_Leaps_tbl.PossibleWeekEndingDates
WHERE (((B_ClosedByWeek_CARs_Tbl.Problem_Location)="KOJ Cherry St" Or (B_ClosedByWeek_CARs_Tbl.Problem_Location)="KOJ Panel Plant" Or (B_ClosedByWeek_CARs_Tbl.Problem_Location)="KOJ Wood Plant") AND ((B_ClosedByWeek_CARs_Tbl.WEDate)<Now() And (B_ClosedByWeek_CARs_Tbl.WEDate)>#5/31/2010#))
GROUP BY CAR_Possible_WEDATES_W_Leaps_tbl.PossibleWeekEndingDates
ORDER BY CAR_Possible_WEDATES_W_Leaps_tbl.PossibleWeekEndingDates;
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
10-
9
20 Comments
Active today
Try changing your criteria to include NULL values for WEDate.
With your right join, these will be NULL for dates that are not present.
I think this will do it for your WHERE clause:
With your right join, these will be NULL for dates that are not present.
I think this will do it for your WHERE clause:
WHERE (((B_ClosedByWeek_CARs_Tbl.Problem_Location)="KOJ Cherry St" Or (B_ClosedByWeek_CARs_Tbl.Problem_Location)="KOJ Panel Plant" Or (B_ClosedByWeek_CARs_Tbl.Problem_Location)="KOJ Wood Plant") AND (((B_ClosedByWeek_CARs_Tbl.WEDate)<Now() And (B_ClosedByWeek_CARs_Tbl.WEDate)>#5/31/2010#) OR B_ClosedByWeek_CARs_Tbl.WEDate IS NULL))
No. That didn't workl. It's Still skipping some weeks. I thought a Join with a list of possible dates would return nulls for those weeks for which no data existed...not just skip them.
Active today
It should... I believe it is your criteria that is preventing that from happening.
Can you post a sample?
Can you post a sample?
Sorry. I should have included this. This is the query output. It is clearly skipping 8/14/2010.
Skipped-Date-1.jpg
Skipped-Date-1.jpg
Active today
Understood - If you are able to post an actual sample DB, it might be easier to work with.
I can't really post the db. These tables are made by make table queries that query Linked tables that are part of a very large db.
Active today
Sorry - I think I'm not being clear... I understand the problem you are having with the missing weeks.
Are you able to post an actual sample database (not just screenshots)?
Are you able to post an actual sample database (not just screenshots)?
Active today
For now, run this test...
Take out the date criteria altogether (I realize this will not yield the correct results).
Do the missing weeks show up with the date criteria gone?
Take out the date criteria altogether (I realize this will not yield the correct results).
Do the missing weeks show up with the date criteria gone?
Yes. You are correct. It is the WHERE clause. I'm not sure how, or if, I can get there from here. I may need to split the data table into a separate table for each location. As soon as I stipulate the location inclusion in the WHERE, it skips the blanks because they aren't associated with the blank dates....because they're blank.
blank-dates-no-criteria.jpg
blank-dates-no-criteria.jpg
Active today
Give this a try...
Instead of using the WEDate from the table that has missing weeks, use the PossiblWeekEndingDate from the table with all of the dates as your criteria. Like this:
((CAR_Possible_WEDATES_W_L
Instead of using the WEDate from the table that has missing weeks, use the PossiblWeekEndingDate from the table with all of the dates as your criteria. Like this:
((CAR_Possible_WEDATES_W_L
Try this:
SELECT Count(NZ(B_ClosedByWeek_CA
CAR_Possible_WEDATES_W_Lea
INTO C3_ClosedbyWeek_KOJ_Time_L
FROM CAR_Possible_WEDATES_W_Lea
LEFT OUTER JOIN B_ClosedByWeek_CARs_Tbl ON B_ClosedByWeek_CARs_Tbl.WE
WHERE (B_ClosedByWeek_CARs_Tbl.P
Or B_ClosedByWeek_CARs_Tbl.Pr
Or B_ClosedByWeek_CARs_Tbl.Pr
AND B_ClosedByWeek_CARs_Tbl.WE
GROUP BY CAR_Possible_WEDATES_W_Lea
ORDER BY CAR_Possible_WEDATES_W_Lea
SELECT Count(NZ(B_ClosedByWeek_CA
CAR_Possible_WEDATES_W_Lea
INTO C3_ClosedbyWeek_KOJ_Time_L
FROM CAR_Possible_WEDATES_W_Lea
LEFT OUTER JOIN B_ClosedByWeek_CARs_Tbl ON B_ClosedByWeek_CARs_Tbl.WE
WHERE (B_ClosedByWeek_CARs_Tbl.P
Or B_ClosedByWeek_CARs_Tbl.Pr
Or B_ClosedByWeek_CARs_Tbl.Pr
AND B_ClosedByWeek_CARs_Tbl.WE
GROUP BY CAR_Possible_WEDATES_W_Lea
ORDER BY CAR_Possible_WEDATES_W_Lea
lludden:
Thank you, but that still skips the weeks that are nulls. (See Below)
I tried a double join, joining the data with both the possible dates and the possible locations, but Access couldn't handle it. It gave me the "ambiguous join" message that I needed to use a subquery. I have yet to successfully put one of those together.
Skipped-Dates-2.jpg
Thank you, but that still skips the weeks that are nulls. (See Below)
I tried a double join, joining the data with both the possible dates and the possible locations, but Access couldn't handle it. It gave me the "ambiguous join" message that I needed to use a subquery. I have yet to successfully put one of those together.
Skipped-Dates-2.jpg
mbizup:
Thank you. Yes. I did. It did not make a difference. When I removed the plant location, it showed the problem.
The data is in the form of Plant Date CAR_Number
When I join that data with the Possible Dates, but don't restrict the Plant, I get the nulls. That is what I want. However, since it only returns one null for a given possible date, and that is not associated with a plant location, by restricting location in the WHERE clause, I filter out the nulls.
Thank you. Yes. I did. It did not make a difference. When I removed the plant location, it showed the problem.
The data is in the form of Plant Date CAR_Number
When I join that data with the Possible Dates, but don't restrict the Plant, I get the nulls. That is what I want. However, since it only returns one null for a given possible date, and that is not associated with a plant location, by restricting location in the WHERE clause, I filter out the nulls.
Active today
It's taking me a bit to get my brain wrapped around your last comment, trying to visualize what you are describing. It's one of the more challenging questions I've seen posted here in a while :)
If I'm understanding correcly, the 'missing' records you want have nothing in the Plant field and nothing in the date field, beause there is no data from your main table corresponding to the right-joined data in your "all dates" table.
You might be able to resolve this by revising your plant criteria to allow NULL plants, or maybe a combination of Null Dates and Null plants
Like this:
WHERE ((B_ClosedByWeek_CARs_Tbl.
Or This:
WHERE ((B_ClosedByWeek_CARs_Tbl.
If I'm understanding correcly, the 'missing' records you want have nothing in the Plant field and nothing in the date field, beause there is no data from your main table corresponding to the right-joined data in your "all dates" table.
You might be able to resolve this by revising your plant criteria to allow NULL plants, or maybe a combination of Null Dates and Null plants
Like this:
WHERE ((B_ClosedByWeek_CARs_Tbl.
Or This:
WHERE ((B_ClosedByWeek_CARs_Tbl.
mbizup: I believe your assessment is correct. I can find dates with no data (nulls) by joining the dates with data table to the possible dates table, but that returns one null per date with no data. The problem is that there are four locations, so I need to do that for each locations, essentially asking a query to tell me what data is NOT there for four different locations at each of the possible dates.
If three plants had no data for a date, but one did, I would need the one plant's data for that date and three nulls for that date, one for each separate location that had no data. It's probably possible, but I am working right now on breaking it out....doing it with a query by plant, rather than one very clever query.
I will try what you have suggested though. I would much rather reduce my queries by 75%.
If three plants had no data for a date, but one did, I would need the one plant's data for that date and three nulls for that date, one for each separate location that had no data. It's probably possible, but I am working right now on breaking it out....doing it with a query by plant, rather than one very clever query.
I will try what you have suggested though. I would much rather reduce my queries by 75%.
Featured Post
On-screen guidance at the moment of need enables you & your employees to focus on the core, you can now boost your adoption rates swiftly and simply with one easy tool.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
This article describes two methods for creating a combo box that can be used to add new items to the row source -- one for simple lookup tables, and one for a more complex row source where the new item needs data for several fields.
This article describes a method of delivering Word templates for use in merging Access data to Word documents, that requires no computer knowledge on the part of the recipient -- the templates are saved in table fields, and are extracted and install…
Get people started with the utilization of class modules. Class modules can be a powerful tool in Microsoft Access. They allow you to create self-contained objects that encapsulate functionality. They can easily hide the complexity of a process from…
Add bar graphs to Access queries using Unicode block characters. Graphs appear on every record in the color you want. Give life to numbers.
Hopes this gives you ideas on visualizing your data in new ways ~
Create a calculated field in a query:
…
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month8 days, 9 hours left to enroll
617 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.