Ken,

You are right regarding narrowing down the problem! Getting info on Outlook
security is a bit of a pain. I think it is obfuscated on purpose to confuse
malcontents!

Regarding the "Application", that is sort of what I thought, but wanted to
be sure.

Thanks for all the help!

Don





"Ken Slovak - [MVP - Outlook]" wrote in message
...
Application.GetNameSpace() only has meaning in an Outlook VBA project. In
a
Word VBA project "Application" is Word, in an Excel VBA project it's
Excel,
etc. So if not in Outlook then you must use an explicit
Outlook.Application
object and instantiate it.

If objRecip.Application.IsTrusted == false then that definitely explains
why
you aren't getting a Recipient object, Outlook doesn't trust your code.
Why
that is I have no idea.

See if any of the Outlook 2007 specific information at
http://www.outlookcode.com/article.aspx?id=52 gives you any clues as to
what's going on. At least you now know it's a trust issue and not a coding
issue.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Don" wrote in message
...