Hi Ken,
the user creates a new folder entry by posting a custom form. When the form
is posted the script code inside it (within the write event) looks for a
specific hidden item (it uses CDO to perform this operation) in the same
folder whose message class is "IPC.Counters", reads a custom property named
counter and increments it.
I gave the users permission to read,write and delete any items in the folder
but not the ability to delete or add subfolders to this folder.
It happened that the hidden item couldn't be updated. So I extended the
permission to 'Owner' and now it works fine.
The fact is that I'd prefere not to give such a wide permission o prevent
the user to accidentally remove the folder or add subfolders to it or change
the folder permissions.
Max
> So what is the question then? A hidden item by definition is never
> seen in the UI.
[quoted text clipped - 18 lines]
> > property holding the counter value.
> > Max Carussi - [JAD - MS Platform]
Ken Slovak - [MVP - Outlook] - 29 Jan 2004 15:35 GMT
Did you try one of the "publishing" permissions?
I suppose another alternative would be to use a specific dynamic logon
to CDO instead of a piggy-backed logon. In that case you could use
logon information that has permissions as Owner. You could encrypt
that information in the registry or an INI file or something and read
it in and decrypt it on the fly so it wouldn't be hard coded into the
form code.
See some of the different logon code samples at
www.cdolive.com/cdo5.htm for examples of using different logons in
CDO.
--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginners Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm
> Hi Ken,
>
[quoted text clipped - 12 lines]
>
> Max