The OpenEdge DB-to-ODBC migration utility does not literally translate definitions for OpenEdge fields into columns in your target data source. It automatically makes adjustments in the target data source in order to provide the functionality of the OpenEdge and target systems.
If your foreign data source supports all the functions of being compatible, the OpenEdge DB-to-ODBC utility will create the objects in the ODBC data source. It converts arrays by using one column in the ODBC data source for each extent of the OpenEdge array. The utility generates names for the columns that it adds to a table in a target data source using the format field–name##extent–number. For example, an OpenEdge field called monthly–amount with an extent of 12 will have 12 columns in the data source with names such as MONTHLY_AMOUNT##1 through MONTHLY_AMOUNT##12. In DB2 UDB, however, you must name these columns column-name__1, column-name __2, and so forth. (Some DB2 UDB OS environments have trouble translating the pound sign (#) in object names.)
