Information

Title	Frame segment exceeded when compiling after migrating to OpenEdge 10

URL Name	P74659

Article Number	000156733

Environment	Product: OpenEdge Version: 10.x OS: All supported platforms

Question/Problem Description

Frame segment exceeded when Compiling Application Code after migrating to OpenEdge 10.

Error 3307 compiling 4GL / ABL code.

The same code compiles without errors in Progress 9.1x.

Steps to Reproduce

Clarifying Information

Upgrade from Progress 9.1x to OpenEdge 10.x.

Error Message	<segment-name> has exceeded its limit of <segment-size> bytes, in <file-name> at line # <line-number>. (3307) A Frame Segment has exceeded its limit of 32767 bytes, in <file-name> at line # <line-number>. (3307)

Defect Number

Enhancement Number

Cause

In OpenEdge 10, r-code offsets have been expanded from 16-bit to 32-bit.
However, frame segments are still limited to 32K in size.
Due to the expanded r-code offsets, the Frame Segment limit is exceeded which results in error 3307.

Resolution

Upgrade to OpenEdge 11.0 or later.

The Frame Segment limit was resolved with the r-code version change associated with release 11.0.

Workaround

Modify the code to reduce Frame Segment size.

For example,

Use multiple frames.
Use dynamic instead of static widgets.
Remove LABELS (with the NO-LABEL option) from the DISPLAY statement.

Or any combination of the above:

Notes

Progress Articles

P76964, Has there been r-code segment size limit increases in OpenEdge 10.0A?
P113045, How to compile 64-bit r-code ?
P122088, What is the segment size limit of a procedure?

Keyword Phrase

Last Modified Date	1/9/2017 9:56 AM

Frame segment exceeded when compiling after migrating to OpenEdge 10

Information