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.
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.
Building DDFs for your Btrieve database can be the largest undertaking of a migation project. Without DDFs, your data will be read as a conglomeration of meaningless bytes. Validating DDF’s is a listed prerequisite rather than an optional step that you will need to perform before migration.
Magic eDeveloper advertises multi-dbms support through “gateways”. You design the app once and simply configure the backend gateway to one of many. However, if the application is designed for ISAM (Btrieve), then getting it to run against a SQL backend has many challenges.
This happens if you do not have the MS SQL Server \binn directory or the Btrieve\bin directories in your path. We need both those libraries to make the connection. IF it is not found, then we cannot continue and hence the buttons are greyed out.