Services Partners Company
Knowledge Base


Article

How to specify multiple field pairs in a Prodataset DATA-RELATION?

« Go Back

Information

 
EnvironmentAll Supported Operating Systems
OpenEdge 10.x
Question/Problem Description

How to specify multiple field pairs in a ProDataSet DATA-RELATION?


What is the syntax for relating a parent and a child tables of a DATASET with multiple fields?
How to specify multiple pairs in the RELATION-FIELDS attribute of a DATA-RELATION?
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
Resolution
The syntax of defining a DATASET with a DATA-RELATION that has multiple pairs of RELATION-FIELDS is:

DEFINE DATASET DataSetName FOR Parent, Child
DATA-RELATION DataRelationName FOR Parent, Child
RELATION-FIELDS (parent-field1, child-field1, parent-field2, child-field2,. . ., parent-fieldn, child-fieldn)


For example:

DEFINE DATASET DataSetName FOR Parent, Child
DATA-RELATION DataRelationName FOR Parent, Child
RELATION-FIELDS (parent-field1, child-field1, parent-field2, child-field2, parent-field3, child-field3)
Workaround
Notes
Attachment 
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.



Feedback
 
Was this article helpful?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful.



Characters Remaining: 255