Setting property does not work at some clients

[Peter Suba]

This is rather strange.

We have a custom ticketing application that keeps the tickets connected
through the conversationTopic property.

There is part of the code where sub-actions are created as another item in
the folder (a message item derived from Post), and then immediately the
ConversationTopic is set.
However, for some users accessing this application, this part does not work.
For most perople it works perfectly, but we have one person, for whom this
single property does not seem to be set - all other properties are set OK
but this one. Here is the code snippet:

Set oUDMsg = oMsgs.Add("IPM.Post.Ticketing list display form")
oUDMsg.Subject = "Action: Reply message sent"
oUDMsg.ConversationTopic = ConvTopic

' MsgBox "Convtopic,oUDMsg.ConversationTopic:
"&ConvTopic&","&oUDMsg.ConversationTopic

oUDMsg.ConversationIndex = objCurrentMsg.ConversationIndex &
Util_GetEightByteTimeStamp()
oUDMsg.Body = oFormPage.Controls("txtAction").Value
oUDMsg.UserProperties("Ticket Type").Value = Item.UserProperties("Ticket
Type").Value
'(... Other custom properties are set here)
oUDMsg.ReceivedTime = Time
oUDMsg.Unread = True
oUDMsg.Save

If I uncomment the MsgBox above, it clearly shows the the ConversationTopic
property is not the same as ConvTopic (BTW the ConvTopic variable is set
earlier from the original message's ConversationTopic property, and even if
I replace ConvTopic variable with the direct reference to the other valid
ConversationTopic reference here, it is the same result)



The strange part is, that the above code snippet produces similar results
for more users, but not all.
However, if I add the following code after the above snippet:

eID = oUDMsg.EntryID
Set oUDMsg = Nothing
Set objMessage = olemsg.GetMessage(eID,strstoreID)
objMessage.ConversationTopic = ConvTopic
objMessage.ConversationIndex = objCurrentMsg.ConversationIndex &
Util_GetEightByteTimeStamp()
objMessage.Update

Then for most users, the code works and ConversationTopic gets set
perfectly. But even then one user sees the same problems.
However, this additional code should not change the behavior anyway.

Can someone tell me what is happening here?

Clients are all Outloo 2003, but same thing happened with Outloon 2002.

Thanks
Peter

 

[Ken Slovak - [MVP - Outlook]]

ConversationTopic and ConversationIndex are read-only properties in the
Outlook object model. In CDO 1.21 they can be written. But CDO 1.21 is an
optional installation for Outlook 2000 and later. So number 1, does the
problem user have CDO 1.21 installed, since you seem to be using a mix of
OOM and CDO code.

 

[Peter Suba]

Hi Ken,

How do I go about checking if it is installed?

Still seems to be strange that other users sometimes get the same problem,
but not always; also we use the same version of Outlook on the clients
(although users are administrators so it is possible that some things are
installed which should not be)

Peter

 

[Ken Slovak - [MVP - Outlook]]

Well, the easiest way is to see if you get an error on either
CreateObject("MAPI.Session") or on objCDO.Logon. You can also check to see
if CDO.DLL is installed in the user's file system but it might be installed
and not registered correctly.

 

[Peter Suba]

That was it.

Installed CDO and it is working immeditely.

Thanks for Your help.

Peter