Processing activities that require additional action
The following processing activities require the defined action to successfully convert existing 32-bit INTEGER columns to 64-bit INT64 columns:
When existing r-code references a column's original 32-bit INTEGER definition, you must recompile the code and check the table's Cycle Redundancy Check (CRC).
Contrast the actions required to perform the following data definition changes:
If you change data definitions in your original OpenEdge database from INTEGER to INT64 and you had previously migrated your database to an MS SQL Server, you must repeat the migration step to change the field's physical storage on the foreign data source.
If you change data definitions in your original OpenEdge database from INT64 to INTEGER and you had previously migrated your database to an MS SQL Server, you must repeat the migration step to change the field's physical storage on the foreign data source, and then dump and reload the field's data.
If you changed your native definition to include a bigint data type, it is recommended that you repeat the step to pull the table into your schema holder. Otherwise, a conversion from the native bigint data type might occur at run-time if your schema holder defines a different data type. Also, if the schema holder definition of the native bigint is INTEGER, an overflow condition might occur when accessing data in the foreign data source.
When existing r-code references a column's original 32-bit INTEGER definition, you must recompile the code and check the table's Cycle Redundancy Check (CRC).