Forum Replies Created
-
AuthorReplies
-
hi,
thanks!
Would you know if there is a way of hidding that context menu?
Also, if possible, when known could we be updated on a fix?
thanks,
samHi,
thanks for the help.
We are: Windows XP on a Novell Network with Groupwise 7.0.3 installed.
Yes all work stations tryed result in this behavior.
Thanks for any help in advance.
sam
I want to hide in the viewer. yes.
But also not show the file (hide) when a user is viewing the email.
This way the user couldn’t try to view it.
thanks,
Yes i can delete attachments on the composingitem as it is perhaps open.
But on it’s saved draft copy I cannot.
So that is probably the issue.
The only way I can see of solving this is to remove all attachments from the X00 email and then save as a draft. Then put the attachements back on the X00 and then send and send the draft.
any other way? which would make more sense?
sam
I have informed Novell of he Attachments.Add(Message, DisplayName) Defect. they will be looking into it.
I figured i would post the code…
' GroupWise 7+ onwards contains a localized word 'Home' after the account name. ' You will need to add the localized 'Home' after the name if (groupwise.EnvVersionName > "7") then iWIPPath = GroupWise.Account.Owner.DisplayName & " Home" & GroupWise.Account.WorkFolder.Name else iWIPPath = GroupWise.Account.Owner.DisplayName & "" & GroupWise.Account.WorkFolder.Name end if ' Save the draft message to the Work in Progress folder Groupwise.ItemSaveMessageDraft iWIPPath iBreakCount = 0 while (iMsgID = "Token failed execution!") or (iMsgID = "X00") Application.ProcessMessages utilities.Timer 1 Application.ProcessMessages iMsgID = GroupWise.ItemMessageIDFromView iBreakCount = iBreakCount + 1 Utilities.Trace iBreakCount & ": " & iMsgID if (iBreakCount > 10) then exit sub end if wend set oMsg = GroupWise.Account.GetMessage(iMsgID)
I am having a problem with:
' delete all attachments if oMsg.Attachments.Count > 0 then ' for sndIntCounter = 1 to oMsg.Attachments.Count for sndIntCounter = 0 to GroupWise.ItemAttachmentGetCount(oMsg.MessageID)-1 ' msgbox oMsg.Attachments(sndIntCounter).DisplayName ' oMsg.Attachments(sndIntCounter).Delete groupwise.ItemAttachmentDelete oMsg.MessageID, sndIntCounter next end if
seams to not delete the attachements properly. any help would be appreciated.
As you can see i tryed witht eh Formativ and Groupwise API, as the email is draft at this point.thanks,
sam[This message was edited by sam on September 09, 2008 at 01:16 PM.]
[This message was edited by sam on September 09, 2008 at 01:18 PM.]
ok along these lines….
When i use the ItemMessageSave function and then attached the save message to another email using the Groupwise API Attachements.add(File, ,DisplayName) Method.
The attached email looses it’s text formating.
Is this the same issue then the subject?
I have to use this as the Groupwise API Attachements.add(Message, DisplayName) Method does not use the DisplayName supplied for the file.
[This message was edited by sam on September 08, 2008 at 11:37 AM.]
yes this code worked, I a utulizing it but the WIP folder is different in GW 7.0 so i added the groupwise 7 check.
holy shit!
your the smartest guy i know… Proven this code works. I’ll let you know in 2 weeks. Now off to Jamaica
thanks!
thanks for your reply.
Yes it is but i figured diff property diff problem…
I am using the composingItem Formativ object.
I cannot use the Object API the Item has not been sent yet.
Then this begs the question : How can i access the object if it is not sent? Basically how does formativ do it?
thanks,
Thanks for the reply and invertigation.
To work around this I was wondering how could I return the RTF property of the Subject (Novell API) in Formativ for my composingItem.
Then I would in code handle parsing it properly. I feel a fix will take forever from Novell.
Also I there a way for me in Formativ to access the composingItem with the Novell API and not use the Groupwise.ComposingItem object.
thanks,
Hi, We have found that users work stations did not have the SP2 version installed of the msxml dll’s.
Pushing the nez dll solved this issue.
thanks for the help!
-
AuthorReplies