ContentsIndexPreviousNext

7.2 Default Behavior

The following are automatically handled by the Acu4GL product:

4gl90003.gif Acu4GL automatically converts upper case field names to lower case (or vice versa) when necessary, so don't concern yourself with case differences.

4gl90003.gif Acu4GL automatically performs the data conversions needed to match the internal storage formats used by the database.

4gl90003.gif If the database files don't already exist, they will be created for you automatically when you execute an OPEN OUTPUT verb. If this is your situation, you'll have no concerns about matching COBOL fields to database fields. The fields will match perfectly, because the database fields will be based on your COBOL code.

4gl90003.gif You may encounter unexpected sequencing of data returned from a database. If your COBOL definition does not include alternate keys with duplicates, then the data is returned in key order. If your COBOL definition does include alternate keys with duplicates, then be aware that Acu4GL cannot control the sequence in which the data is returned. The database query optomizer 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.

See also

A-MSSQL-ADD-IDENTITY

A-SYB-ADD-IDENTITY

A-INF-DUPLICATE-KEY

A-ORA-DUPLICATE-KEY