> If Outlook hasn't been started yet, you can use the Namespace.Logon method to start it with a particular mail profile.
>
[quoted text clipped - 25 lines]
> >
> > THANKS!
If Outlook isn't running, you'd want to use either
olns.Logon "profile_name", "", False, True
or possibly
olns.Logon "", "", True, True
This is a standalone Windows application? Check to see whether your anti-virus client has script blocking turned on.

Signature
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx
> Hi Sue -
>
[quoted text clipped - 31 lines]
>> >
>> > THANKS!
DeborahK - 16 Aug 2006 23:20 GMT
Hi Sue -
Thanks again for replying. Just wanted you to know that we figured this out.
In case someone else runs into this - here is what we found:
- The storeID is critical to accessing any shared or public folders - but
only the first time in a session. There was one place in the code that was
messing up the store ID. Oddly enough, the store ID does NOT matter in the
following cases:
(1) Outlook has previously been opened.
(2) The user had followed a path in the code that referenced the folder with
a store ID.
But it *does* matter if Outlook has not been opened and this is the first
time accessing the folder.
Once we got the storeID to be correct in all paths of the code - everything
worked fine...
Thanks again for your assistance!
> If Outlook isn't running, you'd want to use either
>
[quoted text clipped - 41 lines]
> >> >
> >> > THANKS!