B
Bill Wood
Guest
WRT The first example was using the two temp-tables in one dataset with defined relation in the dataset which works ok. The relationships are read in, but there are a lot of other issues with the complex dataset related to filtering, updating, deleting, and some read issues (depending on the schema). That is why this is ‘not a supported use case’. WRT objA is created from datasetA which contains only temptableA objB is created from datasetB which contains only temptableB The relation I want to create is 1-N between these two objects. Assuming you want a 1-M (1 ObjA to Many ObjB) you just need to define the proper Foreign Key / Primary Key relationship. ObjA needs a primary key (e.g. ttSalesRep.SaleRep). ObjB needs a field that is the same datatype as ObjA’s Primary key (and is where the database stores the Foreign key value). For example. oeCustomer.SalesRep (the names DO NOT need to match). Step 1: On the ‘Many’ side (ObjB = oeCustoemr), create a “New OpenEdge Relationship” Step 2: Choose the oeCustomer field (SalesRep) that matches the Primary Key of the other related OE Service Object. In this case you want a oeCustomer.SalesRep to be the relationship to the ttSalesRep.SalesRep Primary key. Step 3: Select the appropriate link type (Many-1)
Continue reading...
Continue reading...