Migrating Overlap With DESCENDING Segments

While converting database of a file, there's a migration problem in Flex2SQL. The error seems to indicate a problem creating the inverse key for overlap field.


This issue happens because a bug in DataFlex. It shouldn't allow an OVERLAP field to be a case insensitive segment. You can set this attribute when creating the new index. Next time you open the file with DFFILE you won't allowed to touch on this attribute.


In Database Builder you get an "invalid attribute" error message if you try to set an overlap field as a case-insensitive index segment. So this index should be recreated without setting this overlap segment as case-insensitive.

 

Data Security with Flex2SQL and BTR2SQL Connectivity Products

Data Security with Flex2SQL and BTR2SQL Connectivity Products

The most common reason for Enterprises looking to migrate from legacy Btrieve or DataFlex databases is the urgent need to address security and...

Read More
Why Migrate from Btrieve to PostgreSQL and other Relational Databases?

Why Migrate from Btrieve to PostgreSQL and other Relational Databases?

Introduction Many independent software vendors (ISV) and corporate users still rely on applications that use a category of database collective called...

Read More
Four Challenges in Converting COBOL Applications from ISAM Databases to Relational Databases

Four Challenges in Converting COBOL Applications from ISAM Databases to Relational Databases

COBOL applications are the foundation of numerous essential business functions, especially within the banking, insurance, and government sectors....

Read More