J
John Bailo
I have some Outlook interop code that reads through email in a folder
and reads the body text.
This code runs fine on my workstation, which is an XP machine, 1G/RAM, 2Ghz.
However, when I tried to migrate it to a server, it hangs on the piece
of code that takes the .Body property and tries to pass it to a String:
mailBody = mymailItem.Body;
This machine is a w2k machine, 1G/RAM, 1Ghz.
I'm wondering if there's some sort of latency problem where
communication with the Exchange server is just too slow for the code to
read in the text.
Is there anything I can do? Is there a timeout parameter or something
I can set that would allow this code to run on the slower machine?
and reads the body text.
This code runs fine on my workstation, which is an XP machine, 1G/RAM, 2Ghz.
However, when I tried to migrate it to a server, it hangs on the piece
of code that takes the .Body property and tries to pass it to a String:
mailBody = mymailItem.Body;
This machine is a w2k machine, 1G/RAM, 1Ghz.
I'm wondering if there's some sort of latency problem where
communication with the Exchange server is just too slow for the code to
read in the text.
Is there anything I can do? Is there a timeout parameter or something
I can set that would allow this code to run on the slower machine?