Corrected example ...

    PROPERTY <GroupWithAllItems> VISIBLE 'FALSE'
    PROPERTY <GroupWithLimitedItems> VISIBLE 'FALSE'
    IF (CVAL('NetUser')) = 'johndoe' THEN
        PROPERTY <GroupWithAllItems> VISIBLE 'FALSE'
        PROPERTY <GroupWithLimitedItems> VISIBLE 'TRUE'
    ELSE
        PROPERTY <GroupWithAllItems> VISIBLE 'TRUE'
        PROPERTY <GroupWithLimitedItems> VISIBLE 'FALSE'
    ENDIF
    RETURN

Have fun!

Very Best R:egards,

Razzak.


At 11:50 AM 2/1/2005, Jan Johansen wrote:


I may have painted myself into a corner.

I have been using the Group Bar as a Menu System as outlined
in several of Razzak's samples.

I new that I could use the property id to disable/enable portions
of object. However I just discovered that I there does not appear
to be a component id for 'ITEMS' in a group.

I had hoped to utilize the property command to disable/enable
ITEMS in a group.


Jan,

R:BASE 7.1 for Windows does not include the <Component ID> for
Items within the Group Bar. (No worries in 7.5/V-8 "Turbo")

I have an application with multiple sub-sets of one Group being
displayed on Group Bar based on user access level.

So, in your case:

01. Create a master Group with "all" possible items and a unique
    <GroupWithAllItems>

02. Make a sub-set of master Group with a different Component ID,
    such as <GroupWithLimitedItems>, and delete the items you
    don't need.

03. Based on the user access level, use the PROPERTY command
    accordingly to manage the Groups on Group Bar.

    A very simple example: (On After Start Custom EEP)

    PROPERTY <GroupWithAllItems> VISIBLE 'FALSE'
    PROPERTY <GroupWithLimitedItems> VISIBLE 'FALSE'
    IF (CVAL('NetUser')) = 'johndoe' THEN
        PROPERTY <GroupWithAllItems> VISIBLE 'FALSE'
        PROPERTY <GroupWithLimitedItems> VISIBLE 'TRUE'
    ELSE
        PROPERTY <GroupWithAllItems> VISIBLE 'TRUE'
        PROPERTY <GroupWithAllItems> VISIBLE 'FALSE'
    ENDIF
    RETURN

That is just an example ... You can make it sing, if you wish!

Hope that helps!

Very Best R:egards,

Razzak.



Reply via email to