The following are automatically handled by
- Conversion of uppercase field names to lowercase (or vice versa) when necessary.
- Data conversions needed to match the internal storage formats used by the database.
- Creation of database files, if needed, when you execute an OPEN OUTPUT verb. If this is your situation, matching COBOL fields
to database fields should not be an issue. Fields match perfectly, because the database fields are based on your COBOL code.
As an alternative, you can use your database query tool to create a database.
- Sequencing of data returned from a database: you may encounter unexpected sequencing. If your COBOL definition does not include
alternate keys with duplicates, the data is returned in key order. If your COBOL definition does include alternate keys with
Acu4GL cannot control the sequence in which the data is returned. The database query optimizer decides how to order the returned
records. For a set of records with the same key value, the records may not be in historical order