This discussion is archived
1 2 Previous Next 16 Replies Latest reply: Jan 17, 2013 6:58 AM by 985504 Go to original post RSS
  • 15. Re: FRM-40222
    644060 Newbie
    Currently Being Moderated
    For me this error showed up when I upgraded forms runtime from 6i (Forms Runtime 6.0.8.8.0) to 6i patch 18 (Forms Runtime 6.0.3.27.0).

    To avoid the error:
    - don't set an item's enabled property to false if its required property is true.
    - don't set an item's required property to true if its enabled property is false.

    My fix:

    a) Changed field properties for the particular field w/ the error from:
    enabled = NO and required = YES
    to:
    enabled = YES and required = NO

    b) When programatically making a field required using Set_item_propety, use all of the following commands in the following order:
    set_item_property('my_blk.my_field', ENABLED, PROPERTY_TRUE);
    set_item_property('my_blk.my_field', UPDATE_ALLOWED, PROPERTY_TRUE);
    set_item_property('my_blk.my_field', REQUIRED, PROPERTY_TRUE);

    c) When programatically disabling a field using Set_item_property, use all of the following connands in the following order:
    set_item_property('my_blk.my_field', REQUIRED, PROPERTY_FALSE);
    set_item_property('my_blk.my_field', UPDATE_ALLOWED, PROPERTY_FALSE);
    set_item_property('my_blk.my_field', ENABLED, PROPERTY_FALSE);

    I call this an Oracle "bug" because if you look up "set_item_property" in the Oracle Forms Developer 6i online help the documentation claims that "Propagation of Property Changes" takes care of the conflicts between required and enabled properties.

    Quote:

    Propagation of Property Changes You can only specify a change to one item property at a time through the SET_ITEM_PROPERTY built-in. However, one SET_ITEM_PROPERTY statement can cause changes to more than one item property if the additional changes are necessary to complete, or propagate, the intended change. This is included primarily for compatibility with prior versions.
    The following table shows the SET_ITEM_PROPERTY settings that cause Form Builder to propagate changes across item properties:

    Setting this property parameter...     To this setting     
    Also causes these propagated changes:
    ENABLED     False     
    - sets the Navigable item property to False
    - sets the Update_Null item property to False
    - sets the Updateable item property to False
    - sets the Required item property to False
    DISPLAYED     False     
    - sets the Enabled and Navigable item properties to False
    - sets the Updateable item property to False
    - sets the Update_Null item property to False
    - sets the Required item property to False     
    - sets the Queryable item property to False
    UPDATEABLE     True     
    - sets the Update_Null item property to False
    UPDATE_NULL     True     
    - sets the Updateable item property to False
  • 16. Re: FRM-40222
    985504 Newbie
    Currently Being Moderated
    I migrated forms 60 to 6i. I have the same problem, and I solved changing the property "requered" to 'No' in all of the items that has the problem.
1 2 Previous Next