Custom Form UserProperties-LOCK

[back2grid]

Hi,
Is there anyway i can restrict the user from changing user properties for a
task. The user properties are at folder-level.
something like
Outlook.UserProperty prop = item.UserProperty["TaskProp"];
prop.enabled = false;

CustomPropertyChange event is fired after an property is changed
thanks

 

[Sue Mosher [MVP-Outlook]]

You could store the value of the property somewhere else in the item and replace the value when CustomPropertyChange fires.

 

[back2grid]

Thanks for the reply Sue,
Storing the value of property somewhere else would not solve the problem
entirely.
The issue is i'm retrieving tasks for a person from a external app using
webservices. The tasks has number of properties not supported by Outlook
taskitem. In order to show this i've create customproperties. There are
certain properties (Custom Properties)which i need to ideally not seen by the
user or the least the user can't change. Ideally if i could attach a custom
object to a given item it would be great, but customproperty takes only
primitive data type.

thanks again

You could store the value of the property somewhere else in the item and replace the value when CustomPropertyChange fires.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

Hi,
Is there anyway i can restrict the user from changing user properties for a
task. The user properties are at folder-level.
something like
Outlook.UserProperty prop = item.UserProperty["TaskProp"];
prop.enabled = false;

CustomPropertyChange event is fired after an property is changed
thanks

 

[Sue Mosher [MVP-Outlook]]

If you've created those properties so that they are not defined in the tasks folder, but only in each individual item, then the only way the user can see them would be to put an individual task into form design view. That's an idea highly unlikely to occur to even a fairly sophisticated end user.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

Thanks for the reply Sue,
Storing the value of property somewhere else would not solve the problem
entirely.
The issue is i'm retrieving tasks for a person from a external app using
webservices. The tasks has number of properties not supported by Outlook
taskitem. In order to show this i've create customproperties. There are
certain properties (Custom Properties)which i need to ideally not seen by the
user or the least the user can't change. Ideally if i could attach a custom
object to a given item it would be great, but customproperty takes only
primitive data type.

Hi,
Is there anyway i can restrict the user from changing user properties for a
task. The user properties are at folder-level.
something like
Outlook.UserProperty prop = item.UserProperty["TaskProp"];
prop.enabled = false;

CustomPropertyChange event is fired after an property is changed
thanks

 

[back2grid]

thanks Sue,
In the AddProperties method i was using System.Reflection.Missing.Value
as the object AddToFolderFields method. I changed everything to false. I'm
thinking i'll two sets of values. One item based and one folder based and use
the custompropertychange event to reset changed values.

thanks again sue.

If you've created those properties so that they are not defined in the tasks folder, but only in each individual item, then the only way the user can see them would be to put an individual task into form design view. That's an idea highly unlikely to occur to even a fairly sophisticated end user.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

Thanks for the reply Sue,
Storing the value of property somewhere else would not solve the problem
entirely.
The issue is i'm retrieving tasks for a person from a external app using
webservices. The tasks has number of properties not supported by Outlook
taskitem. In order to show this i've create customproperties. There are
certain properties (Custom Properties)which i need to ideally not seen by the
user or the least the user can't change. Ideally if i could attach a custom
object to a given item it would be great, but customproperty takes only
primitive data type.

Hi,
Is there anyway i can restrict the user from changing user properties for a
task. The user properties are at folder-level.
something like
Outlook.UserProperty prop = item.UserProperty["TaskProp"];
prop.enabled = false;

CustomPropertyChange event is fired after an property is changed
thanks

 

[Sue Mosher [MVP-Outlook]]

That will create fields in the folder. Try using a value of False for that parameter.
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

thanks Sue,
In the AddProperties method i was using System.Reflection.Missing.Value
as the object AddToFolderFields method. I changed everything to false. I'm
thinking i'll two sets of values. One item based and one folder based and use
the custompropertychange event to reset changed values.

thanks again sue.

If you've created those properties so that they are not defined in the tasks folder, but only in each individual item, then the only way the user can see them would be to put an individual task into form design view. That's an idea highly unlikely to occur to even a fairly sophisticated end user.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

Thanks for the reply Sue,
Storing the value of property somewhere else would not solve the problem
entirely.
The issue is i'm retrieving tasks for a person from a external app using
webservices. The tasks has number of properties not supported by Outlook
taskitem. In order to show this i've create customproperties. There are
certain properties (Custom Properties)which i need to ideally not seen by the
user or the least the user can't change. Ideally if i could attach a custom
object to a given item it would be great, but customproperty takes only
primitive data type.

Hi,
Is there anyway i can restrict the user from changing user properties for a
task. The user properties are at folder-level.
something like
Outlook.UserProperty prop = item.UserProperty["TaskProp"];
prop.enabled = false;

CustomPropertyChange event is fired after an property is changed
thanks