I thought the data was extracted from the text files into my SQL database where it is then filtered by my specified date range.

Here are the files but I don't really see what it has to do with my date range.

I am asking it to show data from "90 days ago - Now", but it is giving me a range of years all the way back to 2017 starting with May of 2020. I don't understand the logic, how is that 90 day ago to Now?

I can't work with Audit trail on any 10.4 systems any longer due to the fact that the date range it gives me never matches what I ask for. Only 1 remaining 10.3 version out there continues to work.

That looks like a screenshot from Windows Explorer not from the audit reporter's configuration page. I'm only guessing since the column header is not present, but Dev.log was created on 5/7/2020 and contains information from that date on. So when you asked for "last 90 days", you get that entire log loaded in the database.

How would I be able to define a date range if I am restricted by the size of the log files? Do I need to tell the system to roll over to a new log daily? I don't understand the correlation between log file size and date ranges. From my perspective as a user, I get an option to define a date range on the front end, and I expect to see data for the range I defined.

Your screenshot shows 3 logs from 2017 and one from this year. Like I said, it's not clear to me what date you're showing there, so I can't give you a better guess at what data is in Dev.log.

When you ask for a date range, the server inventories existing logs and loads the ones that cover the requested range in the database for reporting.

But where does the range come in.

For example I said 90 days ago to now. It pulled all 4 logs, which is fine if it want's to do that. But now that it has the data in the database, why am I seeing data for May of this year all the way back to 2017.

I didn't show the bottom of the date range in my screenshot, because even the top of it is enough to show that it doesn't fall in the range I defined.

Regardless of how the system works on the backend, the range should match what is defined.