Is this to store historic data?

Andrew -
Your question doesn't really describe what you are trying to do very well.  The short answer is no, DCount is probably NOT what you need to use.
DCount answers the question "how many?"  For example if I wanted a COUNT of customers that lived in Colorado.

Yes this is for historical data.  I want the database to store how many of an item we had in a certain area of our building when we update the database.

If you are just wanting a record of what was there at a given point in time, yes you could use DCount to append to the history table.  Such as:
3/23/2021    Bay1  5 gold bars
4/01/2021    Bay1  6 gold bars
5/15/2021    Bay1  4 gold bars

The bottom line is YES it can be done, but it all depends on how you have your tables set up, and how much VBA/SQL you know. I see you're only a Beginner user, so I'm not sure how much of this you will understand without further training, but the easiest way to do this in VBA would be (this is pseudocode)...

X = DCount(Records in Query1)
X = X + DCount(Records in Query2)
etc.
DoCmd.RunSQL "INSERT INTO ResultTable..."

So yes. Pretty much ANYTHING can be done. All depends on the specifics. See DCount, INSERT INTO, Intro to VBA

Thanks Richard I will check out the links you have provided.  I have a lot of ideas in my head it is just getting those ideas into my database.  Your video's have been awesome and are my go to when trying out something new!

Glad you like them. :)

I finally got it working thanks for the feedback and suggestions.  This is the code that I ended up using.

If Me.Dirty = True Then Me.Dirty = False 'Save any unsaved data
    Set db = CurrentDb
    Set rs = db.OpenRecordset("AreaHistoryT")
    With rs
        .AddNew
        ![DateTime] = Now()
        ![CountofCarts] = DCount("*", "[IpccCartAge_Q]")
        ![CountofCCS] = DCount("*", "[IpccCcsAge_8_Q]")
        ![CountofFluid] = DCount("*", "[IpccFluidAge_20_Q]")
        ![CountofZone1] = DCount("*", "[Qry_OB_Dwell_Zone1_10]")
        ![CountofZone2] = DCount("*", "[Qry_OB_Dwell_Zone2_10]")
        ![CountofZone3] = DCount("*", "[Qry_OB_Dwell_Zone3_10]")
        ![CountofZone4] = DCount("*", "[Qry_OB_Dwell_Zone4_10]")
        ![CountofST] = DCount("*", "[Qry_OB_Dwell_ST]", "[Dwell Time] >2")
        ![COuntofPB] = DCount("*", "[Qry_OB_Dwell_PB2hr]")
        ![CountofPTSiLPN] = DCount("*", "[iLPN_PTS8_Q]")
        ![COuntofBPiLPN] = DCount("*", "[Qry_iLPN_BP8]")
        ![COuntofOthe

.Update
    End With
    'If you are doing this through a form which is bound to t_Clients,
    'then don't forget you need to requery it to see this addition
    'Next 2 lines are optional depending on the above
    Me.Requery

Looks good. Do you see now why I tell people NOT to use spaces in their table and field names? :)

My Naming Convention has changed thanks to you mid Development...

Yeah that can be trouble too. LOL. The most important thing is to just remain consistent.