Kbase P70987: Setting the TRACKING-CHANGES attribute on the AppServer to YES for an output dataset handle becomes
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  27/01/2006 |
|
Status: Verified
FACT(s) (Environment):
OpenEdge 10.x
SYMPTOM(s):
Setting the TRACKING-CHANGES attribute on the AppServer to YES for an output dataset handle
When dataset handle is received back in the calling 4GL program the TRACKING-CHANGES attribute becomes NO
CAUSE:
This is normal behavior. We do not marshal tracking changes to prevent customers from accidentally passing a dataset from the client to the server with TRACKING-CHANGES on, and doing a fill on the server ruining their before-image tables.
FIX:
Enable the TRACKING-CHANGES attribute once the dataset handle been passed back to the calling program