How do I rename user defined field names?

[Guest]

Outlook 2003, Version 11, Build 6359
As I add more fields to my contacts database, I sometimes want to change the
name of the field. Currently, I have to make a new field with the new name I
want and copy the data from the old field to the new field and delete the old
field to accomplish my goal.

 

[Sue Mosher [MVP-Outlook]]

And that's what you'll have to continue doing. Once you create a custom property, you can't rename it. So, give some thought to the name before you create the field.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Guest]

Thanks, Sue, for your prompt reply. However, I am not happy with the answer.
To the powers that be at Microsoft, I challenge you to make not only user
defined fields dynamic and renameable, but also program defalt field names.
While you are at it I would also like to be able to change other properties
of the field as well. I use Microsoft as my only contacts database, but I
need more flexibility. Thanks to all who tackle this issue! Wayne Self

 

[Ken Slovak - [MVP - Outlook]]

By the design of MAPI all user defined fields are placed in the named
properties section of all item properties. By definition all named
properties use the property name and the type of field (Long, Boolean,
String8, StringUnicode, Multi-value Binary, etc.) as part of the algorithm
that creates the property tag for the user defined field.

Changing name or type would create a new property tag that would be
completely unrelated to the original tag (other than both being in the named
properties namespace).

While I sympathize with what you want, it would make things easier and more
flexible, it can't happen unless the entire MAPI design for Outlook and
Exchange is scrapped and replaced with a completely different design. Forget
about backward compatibility in that case.

 

[Guest]

Thank you, Ken, for your prompt response. You and Sue have convinced me, for
now, to name my fields more accurately the first time. My Quicken program has
me spoiled by allowing me to rename and recatagorize at will. Outlook is a
excellent program and I enjoy using it. Is it feasible for the program to be
rewritten, for the sake of greater flexibility, and then write a migration
program to take care of the backward compatibility issue?

 

[Sue Mosher [MVP-Outlook]]

With hundreds of thousands of individual Outlook applications in use by millions of users, that's highly unlikely, especially when there is already a solution to handle individual situations like yours.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Guest]

Thanks, Sue! What's the solution?

With hundreds of thousands of individual Outlook applications in use by millions of users, that's highly unlikely, especially when there is already a solution to handle individual situations like yours.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

Write a little code to add the new custom field to the item, copy the data from the old field, the delete the old field, and save the item.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Guest]

Thanks, Sue! I haven't gotten into writing code. So, I'll just take your
original advice for now and get on with life. Thanks again!