Selective Unmatched Query

I am not sure what I am tring to do myself half the time :)
So I took your advice and tried subreports...did the trick...the boss likes the way it turned out. Now for a more challenging one...
What I have is a table for all of the contacts with clients. I run reports weekly and monthly. For this report I have the client ID in the contact table which looks to a query where I have clientid and lastnamefirstname. The report, of course, only shows names for those who have contacts for the duration of the report. What boss wants to see is the clients who are not having any contact for that period of time also. I have tried the unmatched query wizard which only gives me the clientids for clients who have never had any contacts. Is there a way for me to get all of the client names into the report, or even run a different report that gives the clientids of the no contact clients for a certain period? Let me know if you need more info, I will do my best

There is - and I do need more info.
I need the table meta-data as well as names and SQL of any queries you will need involved. Here is an example of how to post table MetaData :
Table Name=tblStudent
Please use the coding I've used (It can be copied in the edit box of a reply to this post).
We may need to use subqueries here, but I'll know better when I have all the information.

OK, Here we go

Client Contact table info

Query for LastNameFirstName

Table for Funding

Here is the query that I use for the report

Since I run multiple reports at the same time I have a form where we input the dates Staff Names and Funding.

I hope this is all you need, let me know if I missed something.

For the moment I'm just subscribing properly to the thread.
I hope to look at it in more depth over the weekend.

This looks as if it might be really complicated, but then again it may be deceptively simple. I can't really go through the SQL for the query as there's just too much there (especially in Access mode SQL - non-tidied version). When it gets that involved it's easier to see in the design view, and even then it can get very hard to follow unless you understand what it's about already.

However, if I understand you aright, you have basically some clients and some contacts. The clients link to the contacts via a client ID (of whatever form).

Currently, you have a LEFT JOIN from the contacts to the clients (All contacts - only matching clients) and you want to show ALL clients, regardless of which have any contacts, but include the contact info for those with any. If that's so then you simply build the query with a LEFT JOIN from the Clients to the Contacts instead of the current version which is basically vice-versa.

Does that help (even make sense)?

I went through the sql on the query and see that all I have is inner join. Do I need to change one of these to left join? Here is a smaller version of the query I am working with

This is still quite involved, and the more involved it is, the more important that the SQL is displayed in a structured manner. I've reformatted the SQL you posted in such a way that it will work in exactly the same way, but tabulated it in such a way that it is much easier to read and understand.
One can now see quite easily (nothing's ever really easy when working with SQL except "SELECT * FROM [Table]") that all the JOINs are INNER JOINs.
Assuming that my assertion in post #5 is correct :

Currently, you have a LEFT JOIN from the contacts to the clients (All contacts - only matching clients) and you want to show ALL clients, regardless of which have any contacts, but include the contact info for those with any. If that's so then you simply build the query with a LEFT JOIN from the Clients to the Contacts instead of the current version which is basically vice-versa.

...then this still needs a bit of fiddling with.
We have Record Sources in the FROM clause :
tblClient (Alias=tC)
qryClientName (Alias=qCN)
tblClientContactWithFunding (Alias=tCCWF)
tblFundingCost (Alias=tFC)

My guess would be that tblClient is client-side and tblClientContactWithFunding is contact side. The others are less obvious. qryClientName is probably client-side too, and tblFundingCost appears to be contact-side.

On the assumption above, I will set out your FROM clause (from FROM until just before WHERE) for you.
Ideally we would want to group the two client-side tables together with an INNER JOIN as well as (separately) the two contact-side tables and then join the two groupings together with a LEFT JOIN. Unfortunately Access can't handle INNER JOINs to the logical right of a LEFT JOIN.