Kbase P107026: Input-Output DataSet completely replaces existing DataSet on .Net client
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
06/03/2006 |
|
Status: Verified
FACT(s) (Environment):
OpenEdge 10.0x
SYMPTOM(s):
.Net client calls program on the AppServer which has a ProDataSet as an INPUT-OUTPUT parameter
When the call to the AppServer is finished the existing DataSet on the .Net client is completely replaced by the returned ProDataSet
This behavior is documented as expected behavior, however, replacing the existing DataSet on the .Net client wreaks havoc with things like Data Binding
CAUSE:
Bug# 20050729-025
CAUSE:
When the INPUT-OUTPUT ProDataSet was sent back from the AppServer to the client we were sending back a completely new ProDataSet. This caused Data Binding to fail because the Data Binding was pointing to the wrong DataSet. Starting in OpenEdge 10.1A, we send back only the new data and not an entirely new DataSet. The new data replaces the existing data in the DataSet on the .Net side so Data Binding will still function normally.
FIX:
Upgrade to OpenEdge 10.1A