OK. First, stick the word "does" between the words "Date evaluation" and "not make sense" up there...

I must admit, i believe this one is from something painfully obvious that i just am way too wrapped up to see right now.

We have a table of transactions with one field being TXDate and another TXPmtCredit (I regret using "TX" but i'll deal with that later).

I run the following SQL on it:
strSQL = "SELECT ([TXPmt]) FROM tblTransaction WHERE [IDAgreement] =" & lIDAgreement & " AND TXDate >" & CDate("01/01/2025")
(i am only using the fixed date at the end trying to sort this issue out, it originally was just Date())

Notice i am writing
TXDate >
???

TXDate was the logged date of the transaction. Before today. Certainly before next New Year's Day.

Each entry in the table for this field has a date that is previous to today, but when i use < i get an incorrect total of 0. When i tried > out of frustration, i get the right answer. I went so far to check in the immediate window whether or not CDate("10/30/2024") > CDate("01/01/2025")
just because i thought i might be "losing it" entirely, but that came back as false as expected. Yet in employing that SQL in a procedure to total a specific field related to a specific Customer for a specific set of dates (simply less than, or before, today), i have to tell it that the transaction dates i want are greater than today's date, or as in the example, greater than next New Year's Day!

I am walking away from this for now; sometimes that is when the answer comes to me, but if any of you see what the heck i am doing wrong i sure would appreciate a shove in the right direction.

Mr. Rost: I NEED MORE SUBJECT LINE SPACE!!! I sound like a caveman! Uhg!