On Mar 1, 12:42 pm, "Dmitry Streblechenko" wrote:
I know nothing aboutREXX.
In C++, you need to call Release() or set the object to null if you are
using smart pointers
In VB, set the object to Nothing
In .Net, set the object to null, then call Marshal.ReleaseCOMObject()

Dmitry Streblechenko (MVP)http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"oorexxpert" wrote in message

oups.com...

On Feb 19, 11:41 pm, "Dmitry Streblechenko"
wrote:
Sounds like you assare running out of 255 RPC channels limit imposed by
Exchange.
How (if at all) do you release messages in the loop?

Dmitry Streblechenko (MVP)http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"oorexxpert" wrote in message

roups.com...

Hello all. First time posting. I am using Outlook 2003 on Windows
XP. I have an application that scans emails in a particular folder.
The folder has about 900 emails in it. The program gets about half
way throught the emails and all of a sudden, it starts getting
80004005 codes when trying to get the body of an email. The program
is written inREXXinstead of VB but I don't think that matters.

Does any one have any idea of what could be wrong or how I would go
about figuring out what is wrong?

Thanks,

John

I didn't. I saw no method that would allow me to free the message.
I'm sure you right because I watch the memory usage of outlook rising
as my program runs. Not only are there many messages, but each one is
fairly big (1,000 lines). Can you tell me how to release the message?

Thanks,

John

I found my problem. It was a problem in the way I was using REXX.