Kbase P175130: AppBuilder-generated code raises error 4062
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/14/2010 |
|
Status: Unverified
SYMPTOM(s):
AppBuilder-generated code raises error 4062
**Attribute <attribute> for the <widget id> was passed an invalid <widget id>. (4062)
**Attribute MOVE-BEFORE-TAB-ITEM for the FRAME <frame name> was passed an invalid widget. (4062)
**Attribute MOVE-AFTER-TAB-ITEM for the FRAME <frame name> was passed an invalid widget. (4062)
AppBuilder generates code similar to the following:
DEFINE VARIABLE XXTABVALXX AS LOGICAL NO-UNDO.
ASSIGN XXTABVALXX = FRAME FRAME-D:MOVE-BEFORE-TAB-ITEM (TOGGLE-1:HANDLE IN FRAME DEFAULT-FRAME)
/* END-ASSIGN-TABS */.
If above code is modified outside of AppBuilder, AppBuilder writes over the changes if the code is later saved in AppBuilder.
FACT(s) (Environment):
Widget adjacent to a frame has the No-Tab-Stop property checked in its Property Sheet.
Windows
Progress 9.x
OpenEdge 10.x
CAUSE:
Bug# OE00200956
CAUSE:
AppBuilder positions frames in the tab order relative to an adjacent widget, but it does not check whether such a widget is in the tab order. Referencing a No-Tab-Stop widget as a tab item generates error 4062.
FIX:
Do not check the No-Tab-Stop box for the widget to be taken out of the tab order. Instead, add the line
<widget name>:TAB-STOP = FALSE.
to the main block before the line executing enable_UI. This will keep the widget in the tab order when it is needed to position the frame in the tab order, but take the widget out of the tab order before the window is displayed.