>Hello all,
>
>I'm sending emails for my customers. There is a cost associated to those emails being sent.
>
>I want to keep a trace of everything I sent. The reason for this is for me to be able to tell them how many emails were sent and to who.
>
>So now I am wondering of the way I shold process this. Should I keep that trace in different tables based on the year of the processing.
>
>For example create new tables for each year. So when the year changes create a new table based on that year. Then I add references of what was sent in that table.
>
>
>Or should I restrict to create two tables. One that will contain a trace of everything and then other one (History) where I will transfer references of what was sent precedent years.
>
>For example this beginning of 2020 I should transfer everything about 2019 in the history table.
>
>
>Any alternative is welcome. How would you process this and why?

I would not use a table per year, unless you are using VFP Tables and the 2GB limit would be reached. I had an application long time ago with yearly tables (those were too large so they had to be split), but when we wanted to have data over multiple years it was always a workaround and not nice to work with. In one table you could easily query a breakdown per year and create reports that span multiple years.