Feedback
Did this article resolve your question/issue?

   

Article

How to access an OpenEdge extent / array field without using PRO_ELEMENT

« Go Back

Information

 
TitleHow to access an OpenEdge extent / array field without using PRO_ELEMENT
URL NameP119998
Article Number000140123
EnvironmentProduct: OpenEdge
Version: 10.1x, 10.2x, 11.x
OS: All Supported Platforms
Other: SQL, SQL92, SQL-92
Question/Problem Description
How to access an OpenEdge extent / array field without using PRO_ELEMENT
How to reference an OpenEdge extent / array field from SQL-92 in OpenEdge 10.1x or higher
How to use index referencing for SQL-92 extent / array fields
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution

Starting in Open Edge 10.1A, extent/array fields can be referenced with an index.

For example, the following statement uses index referencing for the extent field monthquota which exists in the salesrep table of the sports2000 database:

Statement:

SQLExplorer>SELECT monthquota[1] FROM PUB.salesrep;

RESULT:

MonthQuota[1]
-------------
         1600
         1800
         3800
         1600
         3800
         2200
         1800
         4200
         3000

Previously to 10.1A, the PRO_ELEMENT function was needed to access array / extent fields.
 

Workaround
Notes

References to Written Documentation:

Progress Solution(s):

"How to Have Separate Elements in an Array Field with SQL-92"
 

Last Modified Date11/20/2020 7:29 AM
Attachment 
Files
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.