I have a question that pertains to the longte...

[Jesse_Prud_Homm]

I have a question that pertains to the longterm use of my app with the accumulation of rows of data.

I’ve designed an app that captures job details (customer, address, description, etc, etc) and I’ve found after using it for a year I’ve got an excessive amount of rows that I believe might slow down the app.

My question is: how do I design an app so that ‘archived’ jobs are no longer in the ‘active’ jobs table? Is it possible to change a job status and have it disappear from the active table?

I’d like to be able to search and reference archived jobs like normal, but not have to load the table if there are thousands of rows there. Perhaps, a way to make all of last years’ jobs go on a different table than this years’ jobs would also be helpful.