Lookups, Outlines & Hides

Hi, I am using an Outline as a menu which has an entry for each of the 100 views in the database. Each Outline entry has a hide formula which does a lookup and checks to see if the user is a member of the email group which is returned. So, an Outline Entry will only display of the user is a member of it’s associated group. The slight problem with this is that it can sometimes be a little slow opening the database, presumably because of the hundred lookups. Can anyone suggest any way of improving the speed of this please? The lookups check a view in the same database and use the nocache parameter. Is it worth indexing the database?

Many thanks

Regards

Mike

Subject: Lookups, Outlines & Hides

My first question is why you need 100 views in a database? How many actually get used?

I would suggest that you break down the outline into separate outlines, assign roles to the users, and load the outline based on their user role.

Also, How are you preventing them from accessing the views from the menu?

Subject: RE: Lookups, Outlines & Hides

Keeping in mind, of course, that there’s no such thing as view security, really. Oh, you can keep a user from seeing a particular view using the security tab, but if you have a hundred nearly-identical views with different selection formulas, a user can create a private view with no restriction and see any unprotected documents.

Readers fields, categories, and @SetViewInfo are probably the way to go here. That reduces the outline entries from 100 to 1, and reduces the lookups from 100 to 0.

Subject: RE: Lookups, Outlines & Hides

If I could just get @SetViewInfo to behave properly…

Another alternative is to embed the view on a form and have one hidden lookup field on that form> Hide entries based on the value of that field. It will work, as I just tested and an approach I had never thought of.

Subject: Use Readers Field!!! Then it is automatic.

Subject: Use Readers Field!!! Then it is automatic.

Thanks for all your suggestions.

I cannot use Roles because there is a limit on the number you can have, about 60ish? Also I cannot use Reader fields because the users need editor access to their documents. I have tried using a single category view embedded into a form but I haven’t yet figured out the formula I would need as the whole view database is based upon a lookup view which contains user groups so I would need to check which groups the user belings to then display the related category, I am not sure how to do this…

I need the user to be able to open the database, then the view to display the category that is related to a notes group listed in the lookup view. The lookup view displays documents containing Category,Notes Group & Description

I have now removed 98 of the views and have just the one with the displayed category now being chosen by an Outline Entry Action and SetViewInfo. Whilst obviously the database is now far slimmer I still have a speed issue as I still have the 99 outline entries which display dependant on a lookup… any further ideas would be much appreciated, many thanks for your help.

Subject: RE: Use Readers Field!!! Then it is automatic.

see my response above about doing one lookup into a hiden field and hide outline entries based on that field value:

http://www-10.lotus.com/ldd/nd6forum.nsf/DateAllThreadedweb/ba9bd1b6b611329a85256faa00622055?OpenDocument

Subject: @SetViewInfo

This can go a long way to resolving may view complications.