Kbase P100569: DataSet is not generated by ProxyGen when temp-Table has the same definition than another Temp-Table
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/13/2007 |
|
Status: Verified
FACT(s) (Environment):
OpenEdge 10.x
SYMPTOM(s):
Dataset is not generated when temp-Table has the same definition than another Temp-Table included in another Dataset
Generating a .Net proxy via the ProxyGen
.p program contains 2 ProDataSets.
The Temp-Tables have different names
CAUSE:
This is expected behavior.
When you have multiple strongly typed datasets ProxyGen will only generate code for one of them and will define all parameters that refer to any of the strongly type datasets as being of the type of the one strongly typed dataset.
This is done on purpose to promote ease of use and conversion (casting) between the datasets.
FIX:
Add a dummy field in the Temp-Table in order to have a different definition than the other Temp-table.
For example:
DEFINE TEMP-TABLE tt1
FIELD Field1 AS INTEGER
FIELD Field2 AS CHARACTER.
DEFINE DATASET ds1 FOR tt1.
DEFINE TEMP-TABLE tt2
FIELD Field1 AS INTEGER
FIELD Field2 AS CHARACTER
FIELD DummyField AS INTEGER.
DEFINE DATASET ds2 FOR tt2.