The "enab" attribute only works within the context of a specific unit. It
does NOT work across multiple units. The only way to track this (that I can
think of right now) is by using a validation rule. You can't directly
impose the restriction - only a validation can check for it. The method I
would use is to assign a unique type to UnitA, then assign another unique
type to the Option. You can then use a "trat" attribute to ensure that the
existence of type "Option" in the roster requires the presence of type "UnitA".
Hope this helps,
Rob
At 02:09 PM 11/21/2001 +0000, you wrote:
>Hi Folks
>
>I am having problems getting the enab special attribute to work.
>
>I have Unit A and Unit B. When unit A is chosen it allows unit B to
>take an option, but without Unit A, Unit B cannot take the option.
>
>What I have attemted to do is add the Attribute dsab to the option
>and adding the option to Unit B. It shows up as disabled and
>unchangeable.
>
>Then I created an item with the 'enab:UnitB-Option' Attribute and
>Included it with Unit A, in hopes that by choosing Unit A, you would
>make the Option available to Unit B. Unfortunately, Unit B still
>cannot choose the option, even when Unit A has been chosen.
>
>Any help?
>
>Chris
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development
www.wolflair.com
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Promise to Quit
Nicotrol will help
http://us.click.yahoo.com/5vN8tD/AqS...SFAA/IMSolB/TM
---------------------------------------------------------------------~->