Forum Discussion
Steps to remove certain date range of records in Access
If less than 100K, I would not bother. Access is fast enough. Just make sure you have good (duplicate) indexes to assist with looking up data.
Note that you cannot "remove" and "keep" the data at the same time 🙂
If you insist, what you can do is archive the current version of the FE and BE in a folder on the server, just in case you need it in future, and then delete the old data. I insist on archiving the FE as well, as it may evolve over time and become incompatible with today's BE.
To delete data, use a Delete query.
- What does FE and BE stands for?
- The Front End and the Back End of a split database.
- Around 56k. The database opens slowly and the tables open slowly.
Can you quantify "slowly"? Seconds? Dozens of seconds?
What operations, specifically, are slow? Simply opening the accdb and waiting for the first form to settle?
What is the design pattern for opening forms? I.e. are forms bound to unfiltered queries, or even whole tables?
What database engine is used for the back end, accdb? SharePoint lists? SQL Server? Something else?
It's not uncommon for certain design patterns that work okay initially, on small recordsets, to be become increasingly sluggish as the number of records grows. Unfortunate design choices begin to make their impact known over time.
Trust me, I am well aware of that problem. This isn't on the same development platform, but I recently found myself relearning this important principle, even though I've been doing database work for more than 20 years.
The more details you can share about the design of the database application, the more likely someone will have direct suggestions to share. At the end of the process, you may still want to archive older data, but that should be a last resort.
- The database was created many years ago by a former team member who really did not know a lot about relationships or design choices. I could rebuild it, but time is not something I have to do so.
The database takes about 20 seconds to open and land on the Menu. When I click on Relationships Design I see 3 tables, one looks blank because it is link to an Excel spreadsheet for its data.
This database allows our Phone QA person to enter scores when observing phone calls for our Customer Service teams. I believe there are too many tables, queries, reports, etc. that does not mean much, little or improper relationship. She should enter call score data, ensure calculation is returned correctly (this took weeks for me to figure out when scores weren't correctly being outputted).
I consider myself a Novice still after all these years. I need to learn how to create formulas and maybe slowing recreate this tool for her.
Thank you for your insight.
