If it's not broken, why fix it?
Btrieve 6.15 was released in 1994 – a long time ago. Btrieve isn't supported on current versions of operating systems like Windows 7, and wont be supported on future versions. While there may not be compatibility issues today, the next service pack or OS upgrade could "break" your application. If your customer isn't going to add service packs or applications that require an OS upgrade, then there is nothing to worry about. Otherwise, sooner or later, an OS update is going to result in your application failing and a call from your customer.
The only way to solve this problem is to prevent it from happening in the first place – with Pervasive PSQL.
My customers don't care, why should I?
Business owners care more about functionality and performance than software version numbers and bleeding edge technology. They also care about investing in solutions that improve productivity – which is why everybody upgrades eventually. Clients may not care about upgrading your application if it's working, but they will care if they can't use your application with the latest hardware or operating systems.
Don't get left behind.
How can I afford to upgrade?
You know about the risk of staying with Btrieve 6.15. You know that unsupported Btrieve 6.15 applications will fail over time. Knowing that, just how big would the price tag of a failing system be? Your business' health? Your customers?
It's this simple: The financial risk of continuing to use Btrieve 6.15 is many times greater than the lasting investment of upgrading your installed base to Pervasive PSQL.
Where can I find more information about migrating from Btrieve to Pervasive PSQL?