Kbase 17256: Why non-db fields don't clear in Viewer on ADD? 8.1A 8.2A
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Why non-db fields don't clear in Viewer on ADD? 8.1A 8.2A
In version 8.0A, adm-add-record() always did a CLEAR FRAME in order
to blank out all values for a new record. In 8.2A and later versions
of 8.1A this CLEAR FRAME was removed from
tableio.i because it was no longer
needed as Progress was now reliably displaying initial values when
an ADD button was pressed instead of blanking out the entire frame
with a CLEAR FRAME statement.
Removing the CLEAR FRAME statement from tableio.i may cause the
following change in behavior for users migrating from version 8.0A
(and early versions of 8.1A) to later versions of 8.1A and 8.2A:
The behavior change is that pressing the ADD button of a smartPanel
that is linked to a SmartViewer will no longer clear NON-database
fields as it did in version 8.0A and earlier versions of 8.1A.
There are two ways to workaround this:
1. You can create a local-add-record() routine that will clear
the field. This approach can be time-consuming if you have
several smartViewers to change.
-- OR --
2. You can re-insert the statement
CLEAR FRAME {&FRAME-NAME}.
in adm-add-record in tableio.i, just before the statement
DISPLAY {&UNLESS-HIDDEN} {&DISPLAYED-FIELDS}...
Method 2 will restore the earlier behavior without you having to add
local-add-record procedures to all of your viewers.
For recommendations on how to change the underlying ADM code,
please refer to Knowledgebase entry 15815 "Modifying ADM support code".
Progress Software Technical Support Note # 17256