Leading Low Cost Paradox Developers Sydney, Melbourne, Brisbane, Perth, Adelaide
Your records are still in there. Getting them out intact is the job.
For businesses with records in Borland or Corel Paradox tables. We read the tables, memo fields and indexes, move the data to PostgreSQL, SQL Server or another database with the totals reconciled, and replace the application where one is still needed.
More about this service
We are an Australian team working with businesses in the United States, the United Kingdom, New Zealand and Australia. Every engagement starts with a scoped technical assessment, so the estimate that follows is based on your code and your data.
- Assessment A scoped technical review before any estimate
- 18+ yrs Building business software
- Independent No licence commission, no reseller agenda
- US UK NZ AU Australian team, no account managers
Built here. Your data stays here.
- No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
- Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
- Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.
Nobody supports it, and your records are still inside
Paradox was a serious competitor to dBase and Access through the 1990s. The applications that remain are typically membership registers, client records or job books that were built once and never revisited, often running on the one old computer that still has everything installed.
Read more
The blocker is almost never the application. It is getting the data out of the tables cleanly, with the memo fields, the dates and the accented characters intact, and then proving that nothing was lost.
Our Paradox developer service is for businesses in Sydney, Melbourne, Brisbane, Perth and Adelaide. It covers three kinds of work: code fixes and updates, migration to a modern technology stack, and ongoing maintenance and support.
Three ways forward for a Paradox database
For many businesses the first is the whole job.
-
Convert the data
The tables are read and loaded into PostgreSQL, SQL Server, MySQL or another current database, and reconciled table by table. The records are safe, searchable and backed up, whatever happens to the old program.
-
Keep the old system readable
Where the old application still has to be consulted, it is moved to a virtual machine that can be backed up, so it no longer depends on one ageing computer.
-
Replace the application
A web application is built on the converted data, for the screens and reports people still use.
What we do with Paradox systems
Six kinds of work. Most engagements are one or two of them.
-
Table conversion
Paradox tables loaded into a current database, with field types, keys and indexes carried across.
-
Memo and image fields
Long text and pictures held in the paired .mb files brought across with the records they belong to.
-
Characters and dates
Language drivers, accented characters and old date formats handled deliberately, not left to a default.
-
ObjectPAL review
Scripts and forms read for the business rules they contain, and written down.
-
Delphi and BDE applications
Programs written in Delphi or C++Builder that use Paradox tables through the Borland Database Engine moved to a current database.
-
Replacement application
A web application for the lookups, data entry and reports the old system provided.
Data only, a simple front end and a full replacement are different projects
Each is right for a different amount of daily use.
-
Data only
The records in a current database, reconciled and documented. Right for an archive or a register that is consulted now and then.
-
Data plus a simple front end
The same data with screens for finding, adding and editing records. Enough for a system a few people use each week.
-
Full replacement
The forms, rules and reports rebuilt as a web application. Right when the business still runs on it daily.
What a Paradox assessment looks at
Paradox tables are well understood. The care is in the details below. The status of the Borland Database Engine is from Embarcadero documentation.
-
The files
Tables are .db files. Primary indexes are .px files, memo and image data is in .mb files, and secondary indexes and validity checks sit in further files beside them. A copy that leaves any of them behind is incomplete.
-
Table versions
Tables made by Paradox for DOS and by Paradox for Windows differ in what they can hold. The table level decides which tools read a table correctly.
-
The Borland Database Engine
Most Paradox data used outside Paradox itself goes through the BDE. Embarcadero states that the BDE is deprecated and will not be enhanced, and it has not been part of the Delphi installation since XE8.
-
Character sets
Each table carries a language driver. Accented names and symbols come out wrong when it is ignored, and that is the most common fault in a quick export.
-
Passwords
Tables can be password protected. The passwords need to be known before work starts.
-
Shared use and damage
Lock files show the tables were shared over a network. Damaged indexes are common, and are checked and rebuilt on a copy.
-
Forms, reports and scripts
Forms (.fsl), reports (.rsl) and scripts (.ssl) written in ObjectPAL. They are often the only written record of how the process works.
-
What else reads the tables
Other programs, mail merges and exports that open the tables directly, so that nothing stops working unnoticed.
Records in Paradox tables and one old computer that still opens them?
What the assessment needs from you
A fixed-scope piece of work with a written result: the options, the risks of each, and a staged estimate. No production data is sent by email. We agree a secure way to share it first.
-
Version
Paradox for DOS or Windows and its version, or the program that uses the tables if it is not Paradox itself.
-
The files
The folder of tables with every file beside them, and their sizes.
-
The application
Whether people use Paradox forms and scripts, or a separate program written in Delphi or similar.
-
Users
How many people use it, and how often.
-
Reports
The reports the business still needs.
-
Where it should go
The database you want the data in, if you already know.
-
The old computer
Whether the machine that runs it still works, and whether it can be copied.
-
What is hurting
The two or three problems that started the conversation.
From assessment to records you can rely on
By video call and screen share, at meeting times agreed to suit you.
-
Technical assessment
We establish the table versions, the files present, the character set and what else uses the data. You get a written list of options with the risks of each and a staged estimate.
-
A safe copy
The whole folder is copied, so every later step is done away from the original files.
-
Trial conversion
The largest and most awkward tables are converted first, and checked for memo fields, dates and characters.
-
Full conversion and reconciliation
Every table is loaded into the new database. Row counts, control totals and spot checks are given to you in writing.
-
Front end, if needed
Screens and reports are built on the converted data, in stages agreed from the assessment.
-
Cutover and support
Each switch is planned with a way back. We watch the first days of live use, then maintain the system for as long as it stays in service.
What people ask us about Paradox
Can Paradox data actually be recovered?
Yes. The table format is well understood, and the memo fields in the paired .mb files are the part that partial extractions usually lose. Both are read, and the result is reconciled against the original.
Which databases can Paradox data be converted to?
PostgreSQL, SQL Server, MySQL, MariaDB, SQLite, Db2, Access and most others. The target matters less than the checking. The same conversion and the same reconciliation apply whichever is chosen.
We only want the data, not a new application. Is that a job you take?
Yes, and it is often the sensible first step. Getting the data somewhere safe and readable removes the urgency, and the decision about the application can be made later.
The only machine that runs it is very old. Does that matter?
It is the usual situation, and a good reason to start now. The work is done from a copy of the files, so that machine does not need to be kept alive for the extraction.
What about the ObjectPAL scripts?
They hold business rules worth keeping, so they are read as documentation even when the application is being rebuilt from scratch.
How do we know nothing was lost?
Reconciliation. Row counts, control totals and spot checks on the awkward fields, given to you in writing before anything is switched off.
Do you provide Paradox developers in Sydney, Melbourne, Brisbane, Perth and Adelaide?
Yes. We are an Australian team and we take on Paradox work for businesses in Sydney, Melbourne, Brisbane, Perth and Adelaide, and elsewhere in Australia. The work runs by video call and screen share, with secure access to a copy of your system. The service is the same in every city: code fixes and updates, migration to a modern technology stack, and ongoing maintenance and support.
How does this work from the United States, the United Kingdom or New Zealand?
By video call and screen share, at meeting times agreed to suit you, from discovery to handover. Confidentiality, who can reach your systems and where your data is held are agreed in writing before work starts.
What does it cost?
The assessment is a fixed-scope piece of work with an agreed fee. The estimate for anything after it comes from what the assessment finds, in stages, so you are not asked to commit to a whole project on a guess.
Sending your details…
You can stay on this page while we send it.
Tell us about your Paradox database
What the database holds, the Paradox version if known, how many tables there are, and what is forcing the question. Include your country so we can suggest meeting times. Please do not send production data.
Prefer a quick chat? Call 0425 531 127. We answer it ourselves, in Australia.
Kasun Wijayamanna, founderYou deal with Kasun from scope to delivery. No account managers and no offshore handoff.