Property tags - what happens if... (Rename of user defined..

External Since: Feb 20, 2008 Posts: 57

.....but why this strange method is the only one that can "find" existing
Property to copy value from ???
(the loop is above and passes the individual oMail objects to our Function)

Private Function SubAkce_Rename(ByRef oMail As redemption.RDOMail, txtOld As
String, txtNew As String, tt As Long)

If Len(Trim(txtOld)) = 0 Or Len(Trim(txtNew)) = 0 Or IsEmpty(tt) Or tt =
-1 Then Exit Function

Dim ups As redemption.RDOUserProperties
Set ups = oMail.UserProperties

Dim upold As redemption.RDOUserProperty, upnew As
redemption.RDOUserProperty
Set upold = ups.Add(txtOld, tt, True)

If upold Is Nothing Then Exit Function
If IsEmpty(upold.Value) Then Exit Function

Set upnew = ups.Add(txtNew, upold.Type, True)

upnew.Value = upold.Value

'...a smaÅ¾eme starÃ©
upold.Value = Empty
Set upold = Nothing

oMail.Save

Set upnew = Nothing
Set upold = Nothing
Set ups = Nothing

End Function

External Since: Oct 17, 2003 Posts: 2898

I see you using dot operators in your code so what you say just isn't so.

Set oUserProp = item.UserProperties("myProp") uses dot operators, they're
just implied. To not use dot operators you would Set colUserProps =
item.UserProperties, then set a UserProperty object from the UserProperties
collection.

I also have used VB6 for many years in writing many Outlook addins and have
yet to run into horrible memory leaks or crashes because of lots of items in
folders, and I'm talking about thousands of items in folders. So either my
experience is completely different than yours or you are doing something
wrong in releasing items and objects. And there is no garbage collector for
VB6 as there is in managed code.

If a user property is added as a custom field in a form there may be no
Count for UserProperties and the UserProperties named property as seen in
OutlookSpy may not even be there at all. However there probably will be a
MAPI named property of that name and type. Things are not always consistent
or even logical when you use custom properties in custom forms, one of many
reasons why forms aren't robust solutions.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm

"Bert_Bert" <BertBert DeleteThis @discussions.microsoft.com> wrote in message
news:766B0BF6-3392-4D38-896C-C6D9CC01B9C7@microsoft.com...
>> 1. Instead of using the standard CDO property tags use the _W set of
>> tags.
>> For example, for subject instead of using CdoPR_SUBJECT = (&H37001E) use
>> CdoPR_SUBJECT_W = (&H37001F).
>
> well I have several days and weeks of heavy testing and of course I used
> also the unicode PropTag but with the same poor results, so no, as far as
> I
> know and tested, it was not possible, neither documented from anyone who
> would report successful use of unicode+cdo at internet in real life
>
>
>> 2. The Outlook object model will be slower.
> well, Redemption is also slow with UserProperties, but does not have the
> terrible memory leaks
> and usint the same prop tags as before in CDO gives me Unicode results
>
> Regarding the mem leaks, I know I found KB article at microsoft, it is
> confirmed and known problem for years, and workaround in some register as
> far
> as I remember, but the fix also was not of any use, it was ineffective for
> me
>
>
>> Crashes like that are usually because you did not release objects each
>> pass
>> through the loop or were trying to use dot operators. For example instead
>> of
>
> no, I would argue here, of coure I studied how to fix it for a long time
> and
> am aware of these hints
>
> I strictly release every object to Nothing and do not use .dot convention
> But I could not find anything for Visual Basic that would explicxitly
> invoke
> garbage collector
>
> Maybe problem is that I pass oTaskItem object Byref to subprocedure, in
> the
> end of subprocedure release all objects dependant on it, and in the end of
> loop before Next Set oTaskItem = Nothing.
>
> Well, you can do a little test yourself at 1000 items folder, switch on
> your
> Task manager and watch memory while setting some Userproperties and
> Subject
> and so on for every message that has associated Form with VBScript on it.
>
> I will bet you will not be able to write a program in such a way that
> after
> 300+- items the loop crashes and memoory will be full. It is not 1 single
> test, but painful years of hard experiences, not being able to get rid of
> this problem, all Outlook version till 2003 have this bug (2007 not
> tested,
> but believe also).
>
>> using oMessage.UserProperties.Find() you should instantiate a
>> UserProperties
>> collection and then set the specific UserProperty. Each dot operator adds
>> an
>> internal object that isn't released until the procedure ends.
>
>
>> If using .NET code you might have to use Marshal.ReleaseComObject() on
>> each
>> object to fully release it.
> well using .NET was very nice for me because of comfortable object
> oriented
> modern language, but till the moment I debugged sussefully my app Outlook
> addin and wanted to deploy it.
> Then Deploy hell started for me and despite several pages of microsoft
> official documents with exact steps I did not manage to make it work on
> testing machines, perhaps because of access rights problems, and also
> created
> the package of tens megabytes for just single piece of code is not my cup
> of
> coffe so I got back to rigid VB6 (unmanaged).
> I wait with managed code until they make deployment really work and not
> pain
> Smile

>
>> 3. Is oMessage an RDOMail object or what? It isn't an Outlook object is
>> it?
> oMessage I mean Redemption.RDOMail
>
> yes, RDOMail or I also tested RDOTaskItem
> I also tested late binding declaring all as object but the same problem
>
>> is based on MAPI you really should have some knowledge of MAPI to make
>> the
>> best use of Redemption.
> well I look with OutlookSpy to Properties have and some intuitive feeling
> however I do not understand why .UserProperties on Item that I securely
> know contains "customprop" is empty and has count of properties zero.
> i.e. Why I firstly have to ADD the field to see existing value in it.
>