Complex FOR FIRST statement not working anymore in OpenEdge 12.8.x

After upgrading from OpenEdge 12.2 to 12.8, a complex FOR FIRST query utilizing numerous NUM-ENTRIES and ENTRY functions is no longer functioning as expected.

Title
Complex FOR FIRST statement not working anymore in OpenEdge 12.8.x
URL Name
complex-for-first-statement-not-working-anymore-in-openedge-12-8-x
Article Number
000280922
Environment
Product: OpenEdge Version: 12.8.x OS: Windows
Question/Problem Description
Steps to Reproduce
Run the attached procedure "OE12-8-error.p" in the procedure editor to observe the behavior.
Clarifying Information
Error Message
On the FOR FIRST, it will error: Entry 2 is outside the range of list DX. (560) Entry 3 is outside the range of list DX. (560)
Defect Number
Enhancement Number
Cause
Resolution
Workaround
Keyword Phrase
Last Modified Date
4/10/2025 3:46 PM

Was this article helpful?

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.