Leading Low Cost Btrieve Developers Sydney, Melbourne, Brisbane, Perth, Adelaide
Get the data out and proven first. Everything else can wait.
For businesses whose software keeps its data in Btrieve, Pervasive PSQL or Actian Zen files. We work out the record layouts, move the data into SQL Server or PostgreSQL with the totals reconciled, keep the system running, and replace it in stages where that is the right call.
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.
You may be running Btrieve and not know it
Btrieve is rarely the system anyone bought. It is the engine underneath the system they bought, which is why it turns up in accounting packages, dealership software, medical practice systems and manufacturing applications from the late 1980s onward. Many businesses only learn the name when a supplier stops answering the phone.
Read more
The important thing to understand is that Btrieve is not a relational database in the usual sense. It stores records with indexes, and what the bytes in each record mean is defined by the application, or by a set of definition files that may or may not exist. That is why an ordinary database export does not work, and why the first job is always the record layouts.
Our Btrieve 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 Btrieve system
The first is worth doing whatever is decided afterwards.
-
Get the data out and verified
A copy of the data is read into SQL Server or PostgreSQL, with the record count and control totals of every file checked against the live system. Nothing is switched off. The risk of losing the data is gone, and reports can run on the copy.
-
Keep the application, update the engine
Where the application is healthy, moving its data files to a current Actian Zen engine keeps everything working on software that is still maintained. This is often the cheapest way to deal with an old server.
-
Replace the application in stages
The application is rebuilt, or swapped for a packaged product, using the verified data. Old and new run side by side until the numbers agree.
What we do with Btrieve and Pervasive systems
Six kinds of work. Most engagements are two or three of them.
-
Record layout recovery
File and field definitions rebuilt from DDF files where they exist, and from the application and the data where they do not.
-
Data extraction
Records read into SQL Server, PostgreSQL or another database, with counts and totals reconciled file by file.
-
Ongoing replication
A scheduled copy into a SQL database, so reporting tools and other systems have current data while the old application keeps running.
-
Engine and server moves
Data files moved from an old Pervasive PSQL server to a current engine or a new machine, and tested with the application.
-
Reporting
Reports built on the extracted data, including the ones the old system could never produce.
-
Staged replacement
The application rebuilt as a web application, one area at a time, on data that has already been proven.
Extracting, upgrading and replacing are different projects
Each trades cost against how much of the old system remains afterwards.
-
Keep the application and the engine
Lowest cost. The system is backed up, documented and moved to a safe machine. The data is still only readable through the old engine.
-
Keep the application, add a SQL copy
The application carries on unchanged. A reconciled copy of its data in a SQL database feeds reports and other systems. The business still depends on the old application, but no longer on being able to read its files.
-
Replace the application
Nothing depends on Btrieve afterwards. It takes longest, and the risk is in rules that exist only inside the old program, which is why the data is proven first.
What a Btrieve assessment looks at
Most of this is about finding out what the files mean. The current version is from the Actian download and documentation pages.
-
Which engine and version
Btrieve 6.15, Pervasive.SQL, a Pervasive PSQL version, or Actian Zen, whose current release is version 16. The version decides which tools can read the files, and whether the engine still runs on a current Windows Server.
-
Whether definition files exist
DDF files describe the data files as tables and columns so they can be read with SQL. Many applications never shipped them, or shipped ones that are wrong. Without them, the layouts are rebuilt from the application.
-
How the application talks to the engine
Through the Btrieve record interface, through SQL, or both. Applications that use the record interface hold the layout in their own code, and that is where it has to be read from.
-
What is inside the records
Variable length records, several record types sharing one file, packed and binary number formats, and dates stored as numbers. Each needs a rule, and each rule is proven against figures the business trusts.
-
Whether the application source exists
With source, layouts are read directly. Without it, they are worked out from the data and the screens. That takes longer, and is still reliable once reconciled.
-
Owner names and encryption
Files can carry an owner name that restricts access, with or without encryption. It has to be known before the files can be read.
-
The server
An old Windows or NetWare server, the engine licence and user count, and whether the machine can be copied safely before anything else is tried.
-
What depends on the data
Reports, exports and other programs that read the same files. They are mapped so nothing stops working unnoticed.
Data stuck in Btrieve files and a supplier who has gone quiet?
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.
-
Engine and version
Btrieve, Pervasive PSQL or Actian Zen, the version if known, and the server it runs on.
-
The application
Which product sits on top, who supplied it, and whether its source code exists.
-
The files
A list of the data files with their sizes, and any DDF files beside them.
-
Users
How many people use the system, and for what.
-
Reports
The reports the business relies on.
-
Figures you trust
Reports or totals that can be used to prove the extracted data, such as a trial balance or a stock valuation.
-
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 data you can rely on
By video call and screen share, at meeting times agreed to suit you.
-
Technical assessment
We establish the engine, the files, whether definitions and source exist, and what depends on the data. You get a written list of options with the risks of each and a staged estimate.
-
A safe copy
The files and the server are copied, so every later step is done away from the live system.
-
Proof of concept
A few representative files, including the awkward ones, are decoded and loaded into a SQL database, then reconciled against figures you trust.
-
Full extraction and reconciliation
Every file is read and loaded. Record counts and control 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.
-
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 Btrieve
How do we know if we have Btrieve?
Look for .btr, .dat or .mkd files beside the application, a Btrieve DLL, or a Pervasive or Actian service running on the server. Most people discover it only when a supplier stops answering the phone.
Is Btrieve the same as Pervasive PSQL and Actian Zen?
It is the same lineage. Btrieve became Pervasive.SQL, then Pervasive PSQL, and is now Actian Zen. Old data files can generally be read by a current engine, which is often the cheapest first step.
Can Btrieve data be converted to SQL Server or PostgreSQL?
Yes. Once the record layouts are known, the data is loaded into SQL Server, PostgreSQL, MySQL, Db2 or another database, and reconciled by record counts and control totals.
Can data be extracted without the DDF files?
Yes, though it takes longer. Without DDF files the record layout is recovered from the application and the data, then proven by reconciling against totals the business already trusts.
Should we upgrade to current Actian Zen instead of migrating?
Sometimes. It is a sound answer when the application above it is healthy and the need is only for maintained infrastructure. We will say when it is the cheaper route.
Our accounting package uses Btrieve and the supplier is gone. Now what?
That is the most common version of this call. Get the data out and verified first. It removes the risk at once, and lets you choose a replacement package without a deadline forcing the decision.
Do you provide Btrieve developers in Sydney, Melbourne, Brisbane, Perth and Adelaide?
Yes. We are an Australian team and we take on Btrieve 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 Btrieve system
The product that sits on top, the engine version if known, how big the files 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.