Tom,
Suppose you create a table containing the following columns: Tablename: OTS_Options OTS_id PK integer OTS_Security_level FK integer OTS_ID_refer_to integer OTS_name text 100 OTS_Procedure text 100 I suppose you have a table containing a list of allowed security levels, in which case OTS_Security_level will be a foreign key and will have a different name, which refers to the master table The column OTS_ID_refer_to enables you to build up more than one level in the treeview and its content is a value which refers to another row in the table identified by OTS_id Suppose your security levels are: 10 Lowest level : 100 Highest level I assume the security level is stored in the usertable, for example: 50 and is stored in the variable: V_User_Security_level If a user logs in you have to create a TEMPORARY TABLE or VIEW like: (In this case you can create a TEMP table, because the content will not change) PROJECT TEMPORARY T_OTS_Options FROM OTS_Options USING ALL WHERE OTS_Security_level <= . V_User_Security_level Now a temp table is created and this table is UNIQUE for every user (a real powerful tool in R:base) Create the form with this temporary table as treeview in it and it will only show the nodes which are applicable to the current user. Hope this is helps Tony IJntema From: [email protected] [mailto:[email protected]] On Behalf Of TOM HART Sent: woensdag 16 februari 2011 15:21 To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Tree view I am not sure I follow your logic. I have a tree view with various nodes, depending on the security level of the user I would like for nodes to be visible or not. Razz had explained that property visible does not work on tree view. I don't see what a view would accomplish unless you have an example. My problem is not setting the security level it is displaying the results. I used a group bar before and it would work, I just like the look of the tree view better. Tom _____ From: A.G. IJntema <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Wed, February 16, 2011 12:56:57 AM Subject: [RBASE-L] - RE: Tree view Tom, In that case you still are able to use the same kind of solution. Put all your options in a table together with the security level and the procedure which you should be run. Assuming there is a hierarchy in the security level and this level is also stored at the user level you can create a temporary view, when the user starts the application. Only the allowed rows will be visible in the tree view. Put the procedure in a ampersand variable (f.i. V_COMMAND) and then you can run the procedure easily the EEP procedure connected to the tree view, like: RUN &V_COMMAND Hope this helps Tony IJntema From: [email protected] [mailto:[email protected]] On Behalf Of TOM HART Sent: woensdag 16 februari 2011 2:32 To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Tree view No I want to show nodes on a tree view that are accessible or not depending on security level. Tom _____ From: A.G. IJntema <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Tue, February 15, 2011 12:56:57 PM Subject: [RBASE-L] - RE: Tree view Tom, If I understand it correctly you like to show rows of a table depending on the user. If this is the case using Temporary views based upon the user could be the solution for this problem. It works well with me Tony IJntema From: [email protected] [mailto:[email protected]] On Behalf Of TOM HART Sent: dinsdag 15 februari 2011 15:29 To: RBASE-L Mailing List Subject: [RBASE-L] - Tree view I have a tree view and want some nodes to be visible or not depending on user, I can use: property compid enabled 'false' and it works but I cannot get property compid visible 'false' to work Tom Hart
