Leading Low Cost Clipper Developers Sydney, Melbourne, Brisbane, Perth, Adelaide
The data is readable. That takes the pressure off everything else.
For businesses still running a system written in dBase, Clipper or FoxPro for DOS. We keep it running, read the .dbf data into a current database with the totals reconciled, and rebuild the application where it is still in daily use.
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.
Your books still run on software from the DOS days
These systems are older than most of the people asked to maintain them. Clipper compiled to a DOS program, dBase applications ran from .prg files, and both kept their data in .dbf tables. Many now run inside a virtual machine or a DOS emulator on a modern computer, which works until it does not.
Read more
The good news is that .dbf is a documented, readable format. The data can be recovered. The application logic usually can be too, if the .prg source survived.
Our Clipper 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 dBase or Clipper system
They are usually done in this order, and many businesses stop after the second.
-
Keep it running safely
The system is moved to a virtual machine or emulator that can be backed up and restored, with printing working. This buys time without changing anything staff see.
-
Recover the data
The tables, memo files and indexes are read into SQL Server or PostgreSQL and reconciled. From then on the records do not depend on the old program.
-
Rebuild it, or archive it
If staff use it daily, the application is rebuilt as a web application. If it is only consulted for history, a searchable archive is far cheaper, and we will say so.
What we do with dBase and Clipper systems
Six kinds of work. Most engagements are two or three of them.
-
Emulation and virtual machines
A DOS system moved onto a virtual machine or emulator that can be copied, backed up and restored.
-
DBF data recovery
Tables, memo fields and indexes read with the right reader for each format, loaded into a current database and reconciled.
-
Clipper and dBase maintenance
Changes made in existing .prg source where it survives, and recompiled.
-
Recompiling for Windows
Clipper source compiled with Harbour, an open source compiler built to be compatible with Clipper, so the same program runs on current Windows.
-
Archive
History kept in a searchable form with the reports people still ask for, without the old program.
-
Staged rebuild
The parts still in daily use rebuilt as a web application, on data that has already been proven.
Emulating, recompiling and rebuilding are different projects
Each trades cost against how much of the old system remains afterwards.
-
Keep it under emulation
Lowest cost. Nothing changes for staff. The system is safe from hardware failure, and still as hard to change as it was.
-
Recompile for current Windows
The same source and the same screens, running on current Windows without an emulator. It depends on the source being complete and on the libraries the program uses.
-
Rebuild on a current stack
A web application on a current database. Nothing depends on DOS afterwards. It takes longest, and is worth it when the process is still central to the business.
What a dBase or Clipper assessment looks at
The table format is documented and readable. What varies is everything around it.
-
Which product and version
dBase III, IV or 5, Clipper Summer 87 or 5.x, FoxBASE or FoxPro for DOS. They share the .dbf table and differ in their index and memo formats.
-
Index and memo formats
Indexes in .ndx or .mdx files for dBase, .ntx for Clipper and .cdx for FoxPro, with memo text in .dbt or .fpt files. Each needs the right reader, and memo fields are where a careless extraction loses content.
-
Whether the source survived
The .prg source files, or only the compiled program. The data comes out either way. Without source, the logic is rebuilt from the screens and the reports.
-
Code pages
DOS code pages decide how accented letters and line drawing characters were stored. Text comes out wrong if the code page is guessed.
-
Dates and deleted records
Two digit years, and records marked as deleted but never removed. Both need a rule before the data is loaded.
-
How it runs today
A DOS window on old Windows, an emulator, or a virtual machine. Printing to current printers and file locking on shared drives are the usual weak points.
-
Libraries
Third-party libraries linked into a Clipper program for screens, printing or communications. They decide whether a recompile is practical.
-
What else reads the files
Spreadsheets, exports and other programs that open the tables directly.
A DOS system that only runs on one machine?
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.
-
Product and version
dBase, Clipper or FoxPro for DOS, and the version if known.
-
The source
Whether the .prg files exist, or only the compiled program.
-
The files
The data folder with every file in it, and their sizes.
-
How it runs today
The computer, the Windows version, and any emulator in use.
-
Users
How many people use it, and how often.
-
Reports and printing
The reports the business relies on, and what they print to.
-
What is hurting
The two or three problems that started the conversation.
-
The way back
How long the business can run on the old system if a cutover has to be reversed.
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 product, the file formats, whether the source survived and how the system runs today. You get a written list of options with the risks of each and a staged estimate.
-
A safe copy
The whole system is copied and made to run away from the original machine.
-
Data recovery
Every table is read into a current database. Record counts and totals are compared and given to you in writing.
-
Staged work
The work is done in stages agreed from the assessment, each with its own scope and estimate, starting with whatever is hurting the business most.
-
Reconciliation and user testing
Record counts, totals and report output are compared between the old and new, and your staff test the work they do every day.
-
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 dBase / Clipper
We lost the source code. Is the data still recoverable?
Yes. The .dbf format is documented and can be read by itself, so the data comes out whatever happened to the source or the compiled program. Losing the source makes rebuilding the logic harder. It does not put the records at risk.
Can you read the memo and index files too?
Yes. Memo fields and the .ntx, .mdx or .cdx indexes are handled as part of the extraction. Memo fields are where partial extractions most often lose content without anyone noticing.
The system only runs in an emulator. Can you still work with it?
That is a very common situation. The work is done from a copy of the data files, so the emulator does not need to be kept running for the extraction.
Can a Clipper program run on current Windows?
Often. Clipper source can frequently be compiled with Harbour, an open source compiler built to be compatible with Clipper, so the same program runs on current Windows. It depends on the libraries the program uses, and it is tested on a copy.
Is it worth rebuilding, or only archiving?
It depends on whether the process is still live. If staff use it daily, rebuild. If it is only consulted for history, a readable archive with a few reports is far cheaper, and we will recommend that.
What happened to dBase?
dBase still exists as a Windows product from dBase LLC. Clipper was last released by Computer Associates in the 1990s. Neither helps a DOS program directly, which is why the practical routes are emulation, recompiling or rebuilding.
Do you provide Clipper developers in Sydney, Melbourne, Brisbane, Perth and Adelaide?
Yes. We are an Australian team and we take on Clipper 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 dBase or Clipper system
What the system runs, whether you hold the source, how it runs today, 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.