I've never heard of that warning message being associated with that statement. I have no further ideas. You could reinstall Redemption or drop a line to Redemption's developer.

--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54


wrote in message ...
Sorry, the line is:

set Session = CreateObject("Redemption.RDOSession")

But you also earlier wrote "The error message doesn't match the code
statement. That statement is not setting any properties, read-only or
otherwise," which leads me to believe the problem is with the way the
Redemption libraries are being accessed by my computer rather than the
line of code itself.

-Jake

On Jan 18, 12:25 pm, "Sue Mosher [MVP-Outlook]"
wrote:
Since you didn't include the text of the earlier posts, I don't know what statement is the first line.

wrote in ...
Hi Sue, thanks for the info. However, I noticed even if I delete all
the other lines of code except for the first line, I still get the
read only error. Could it have something to do with my write
privileges on my computer?

I installed redemption using the registry and everything installed
properly, so I don't think that is the issue.

Jake

On Jan 17, 2:44 pm, "Sue Mosher [MVP-Outlook]"
wrote:
Did you download and install the Redemption library?

The error message doesn't match the code statement. That statement is not setting any properties, read-only or otherwise.

This is a more likely problem statement:

Msg.Recipients = Recips

You cannot set a Recipients collection like that. Instead, you would need to loop through the Recips collection and, for each Recip.Address, call Msg.Recipients.Add to add that recipient to Msg.

To invoke the script debugger from Outlook 2003, open the item and choose Tools | Forms | Script Debugger. Choose New Instance of Microsoft Script Editor. Find your procedure and use the F9 key to place a breakpoint on the first line. When you click the button, code execution should stop at the breakpoint. You can then step through each statement by pressing the F11 key.

--