Archive for the ‘BTR2SQL’ Category

Obtaining The Version Of The Mertech Driver In Use

Monday, November 9th, 2009

When an application has been ported from Btrieve to a SQL backend and the Btrieve access dll (w3btrv7 or wbtrv32) has been replaced, the application does not have any indication the backend has changed.  Perhaps you would like the application to verify which backend is in use or you want to be sure the correct version of the Mertech driver is installed.  This can be done through a standard BTRV function call using B_EXTENDED_VERSION (5026) defined in mds_btrieve.h provided with our driver SDK.
(more…)

Wrong Version Of Btrieve Installed

Friday, November 6th, 2009

Symptoms

When starting an application, it complains that Pervasive.SQL Version XX is not installed or that an old/incorrect version of Pervasive.SQL is installed.
(more…)

Why is my Btrieve program so slow after a migration?

Thursday, February 19th, 2009

A common cause of unsatisfactory post-migration performance can usually be traced to the index files. To enjoy speedy performance of your Btrieve program it is necessary to create proper index files. BTR2SQL may have failed to create indexes for a number of reasons. The two most common are duplicate data and running out of disk space.

(more…)

What is a good first step before I migrate from Btrieve?

Thursday, February 19th, 2009

Ideally your first step should be to validate the Data Definition Files (DDF’s) in your database.

(more…)

What do I have to do to migrate data?

Thursday, February 19th, 2009

The data migration process occurs in two simple steps:

1. Creation of a table with the same name and file structure as the Btrieve file.
2. Copying of records from the Btrieve file to the table.

(more…)