
When a TopSpeed file fails, the first question is usually "can it be fixed?" The better question is "what is the safest way back to a system we can trust?" Clarion TPS database repair is not one procedure. It is a set of options, and picking the wrong one can cost you more data than the original fault.
This article is for business owners and IT managers who have a damaged TPS file in front of them, or want a plan ready before they do. It assumes you already know the basics of why files get corrupted. If you want that background, read our guide to why Clarion TPS files get corrupted and how to protect your data. Here we focus on the decision itself.
Step zero: freeze the evidence
Whatever route you choose, start the same way. Have everyone close the program, then copy the whole data folder to a separate location and treat that copy as untouchable. Every repair, rebuild or restore below should be rehearsed on a second copy. Preserving the original files gives you the best chance to investigate your recovery options without changing the evidence.
The three paths in Clarion TPS database repair
Almost every recovery lands on one of three paths, or a combination of them.
1. Repair the file in place (on a copy)
This covers rebuilding keys, checking the file structure and extracting what can be read into a fresh file. It tends to fit when the problem is concentrated in a few tables, the records themselves look intact, and the damage shows up as key or index errors rather than missing data.
Strength: a successful recovery may preserve data entered since your last backup.
Limit: a repaired file is only as trustworthy as your verification of it. If records were damaged, rebuilding the index does not bring them back.
2. Restore from backup and re-enter the gap
This fits when damage is widespread, when several tables disagree with each other, or when you cannot establish what is wrong. The cost is the work done between the backup and the failure.
Strength: you return to a known state.
Limit: the gap must be re-created, and a backup that was taken while files were open may itself be inconsistent. Restore it to a separate location and open it before you commit to this path.
3. Rebuild the table or the data layer
Sometimes the real issue is not one bad file but a structure that keeps failing: tables that have grown very large, keys that were never reviewed, or a data layout that does not suit how the program is now used. In that case the lasting fix is rebuilding the table, and in some cases moving selected data to a more robust back end in a controlled step.
Strength: it addresses the cause, not just the symptom.
Limit: it touches program code and data design, so it needs a developer who understands the application and a test plan.
A practical way to choose
Ask these questions in order. The answers usually point to one path.
- Do you have a recent backup that you have actually restored and opened? If yes, restore becomes a real option and a safety net for everything else. If no, find or create one before anything else.
- How big is the gap between that backup and today? A few hours of entries can be re-keyed. Several weeks of orders and invoices is a different conversation.
- Is the damage limited to one table or spread across several? One table with key errors points toward repair. Inconsistent totals between related tables point toward restore or a deeper review.
- Can you tell what the damage looks like? Error messages, record counts and a comparison with a backup tell you whether records are missing or only indexes are broken. If nobody can say, bring in someone who can before attempting anything.
- Has this happened before? A first incident after a power cut is one thing. The same file failing every few months suggests a cause that repair will not remove.
- How long can the business stop? Your tolerance for downtime sets how much verification you can afford before reopening.
What good verification looks like
A file that opens without an error message is not proof that the repair worked. Before staff go back to normal use, check:
- Record counts per table against your backup or last known figures.
- Control totals your business already trusts, such as outstanding receivables, stock on hand or a day's sales.
- Links between tables. For example, every invoice line should still belong to an invoice, and every invoice to a customer.
- Recent transactions, spot-checked against paper, email or other systems.
- The screens and reports your staff rely on, run by the people who know what the right answer looks like.
Keep the damaged originals until you are confident. They may still hold records that a later attempt can extract.
Warning signs that repair is only a patch
- The same table needs fixing repeatedly.
- Errors appear at one particular screen or after one particular action, which suggests a program or locking problem.
- Problems start after a change to the server, the network, antivirus or backup software.
- Nobody knows which build of the program each workstation is running.
- Your only backup is a copy taken while people were working.
In these cases, repair gets you running again, but a follow-up review of the cause is what stops a repeat. That follow-up can include data design, program code, file access behavior and your backup routine.
What to have ready when you call a specialist
Whoever you ask for help will work faster and more safely if you can supply:
- The exact error messages, and the screens where they appear.
- When the problem started and what happened just before it, such as a power cut, a crash or a server change.
- A preserved copy of the whole data folder.
- Your most recent backup and its date.
- The program version and, if you have it, the source code.
- A list of the numbers or reports that prove the data is right.
Repair, then protect the business rules
Getting data back is half the job. The other half is making sure the program still enforces the rules that your business has built up over years: numbering, validations, calculations and exceptions. That is why we take a stabilize-first approach. We secure the data, make the system dependable again and preserve the business rules before suggesting any larger change.
Need help with Clarion TPS database repair?
Clarion Programming Help has 30 years of experience with Clarion software, including TopSpeed-based systems that crash or show data errors. If you are looking at a damaged TPS file, or you want a recovery plan in place before one happens, Contact Us and describe what you are seeing. Back up your data first and hold off on repair attempts until you have spoken to someone experienced.
