Hi Arthur,
confusion is quickly created when trying to describe this.
With the wisdom that a picture can tell more than a thousand words I will try.
See pic000.jpg.
Under the institution content folder we'll create a folder b1, that
contains a subfolder b1_1.
As long as for both folders all system users have read rights there's
no problem.
But, when you restrict the rights on the b1 folder to f.i. only the
system admins (and leave the b1_1 folder unchanged) the whole
insitution content tree will disappear for all users except for the
system admins, because they have rights on folder b1.
You can solve this problem by adding a folder a1 under the
institution content, where all user have read rights (see pic001.jpg).
All users (except the system admins who can see the whole structure)
now will see a tree structure as in picture pic002.jpg, where it
looks like that the b1_1 folder is a subfolder of the a1 folder.
Therefor you need that a1 folder as "the public folder" to attache
the b1_1 folder to.
Hope this explains what I meant with "Creating a public folder above
the first folder will solve the problem".
Henk
At 11:19 21-10-2005, you wrote:
>Henk,
>Thanks for your advice. I discovered the "disappearing" folders
>trick as part of my investigation and figured it was a Bb error that
>actually had some logic to it, ie it throws up the fact that a
>person needs to have rights to all folders ijn the structure to get
>to the desired sub-folder.
>
>I work in folder view all the time so had not noticed the
>difference. I will try that out today just for the fun.
>
>Not sure what you mean by "Creating a public folder above the first
>folder will solve the problem." Do you mean create a public folder
>as the first folder and move all other folders below this one?
>
>thanks,
>Arthur
>
>
>
>Legal disclaimer
>--------------------------
>
>The information transmitted is the property of the University of
>Paisley and is intended only for the person or entity
>to which it is addressed and may contain confidential and/or
>privileged material. Statements and opinions expressed in this
>e-mail may not represent those of the company. Any review,
>retransmission, dissemination and other use of, or taking
>of any action in reliance upon, this information by persons or
>entities other than the intended recipient is prohibited.
>If you received this in error, please contact the sender immediately
>and delete the material from any computer.
>
>--------------------------
|