Why does Outlook.Application.GetNamespace("MAPI") Fail?

[Lee]

Can anyone point me in the direction as to why the following fails?

Set NS = Outlook.Application.GetNamespace("MAPI")

It is done on a server that only has outlook and exel installed (Excel is
the full instlal, outlook is only partially).
--
-Lee

[Tom Ogilvy]

Set NS = Application.GetObject("Outlook.Application").GetNamespace("MAPI")

Would be more what your are looking for. This would require Outlook to be
running at the time.

If it isn't running, use CreateObject instead. See VBA help on GetObject
and CreateObject for examples and explanations.

--
Regards,
Tom Ogilvy

"Lee" <Lee@discussions.microsoft.com> wrote in message
news:D92F45C6-D441-455F-A917-B97B81ABE757@microsoft.com...
> Can anyone point me in the direction as to why the following fails?
>
> Set NS = Outlook.Application.GetNamespace("MAPI")
>
> It is done on a server that only has outlook and exel installed (Excel is
> the full instlal, outlook is only partially).
> --
> -Lee

[Shadhi]

Hi Lee,
I believe the MAPI namespace only works if Outlook is configured for
CIW (Corporate Intranet/Workgroup?), not Internet Mail (or whatever the other
option is). Also, the MAPI namespace is a connection to an MS Exchange
Server, so a "partial" install of Outlook may not be enough to allow you to
use the MAPI namespace. Another possible cause of the problem: trying to get
to the namespace without an instance of the Outlook Application object. Try
this instead:

set myOutApp = GetObject("Outlook.Application")
set NS = myOutApp.GetNamespace("MAPI")

Using GetObject will allow you to use an existing instance of Outlook, if
there is one; otherwise it will create a new instance. If you prefer to
create a new instance anyway, change the first line to:
set myOutApp = new Outlook.Application

Hope this helps!

Shadhi

"Lee" wrote:

> Can anyone point me in the direction as to why the following fails?
>
> Set NS = Outlook.Application.GetNamespace("MAPI")
>
> It is done on a server that only has outlook and exel installed (Excel is
> the full instlal, outlook is only partially).
> --
> -Lee

[Lee]

Okay, I found the problem. It is saying I am missing a .dll file. Does
anyone know what the .dll file I would need for this, its really Excel
running an outlook method. Thanks.
--
-Lee


"Shadhi" wrote:

> Hi Lee,
> I believe the MAPI namespace only works if Outlook is configured for
> CIW (Corporate Intranet/Workgroup?), not Internet Mail (or whatever the other
> option is). Also, the MAPI namespace is a connection to an MS Exchange
> Server, so a "partial" install of Outlook may not be enough to allow you to
> use the MAPI namespace. Another possible cause of the problem: trying to get
> to the namespace without an instance of the Outlook Application object. Try
> this instead:
>
> set myOutApp = GetObject("Outlook.Application")
> set NS = myOutApp.GetNamespace("MAPI")
>
> Using GetObject will allow you to use an existing instance of Outlook, if
> there is one; otherwise it will create a new instance. If you prefer to
> create a new instance anyway, change the first line to:
> set myOutApp = new Outlook.Application
>
> Hope this helps!
>
> Shadhi
>
> "Lee" wrote:
>
> > Can anyone point me in the direction as to why the following fails?
> >
> > Set NS = Outlook.Application.GetNamespace("MAPI")
> >
> > It is done on a server that only has outlook and exel installed (Excel is
> > the full instlal, outlook is only partially).
> > --
> > -Lee

[Tom Ogilvy]

Why not try an Outlook group. You have departed from any dependence on
Excel.

--
Regards,
Tom Ogilvy


"Lee" <Lee@discussions.microsoft.com> wrote in message
news:E4870C15-D1FA-4B99-8D8B-77E4084A5B47@microsoft.com...
> Okay, I found the problem. It is saying I am missing a .dll file. Does
> anyone know what the .dll file I would need for this, its really Excel
> running an outlook method. Thanks.
> --
> -Lee
>
>
> "Shadhi" wrote:
>
> > Hi Lee,
> > I believe the MAPI namespace only works if Outlook is configured
for
> > CIW (Corporate Intranet/Workgroup?), not Internet Mail (or whatever the
other
> > option is). Also, the MAPI namespace is a connection to an MS Exchange
> > Server, so a "partial" install of Outlook may not be enough to allow you
to
> > use the MAPI namespace. Another possible cause of the problem: trying
to get
> > to the namespace without an instance of the Outlook Application object.
Try
> > this instead:
> >
> > set myOutApp = GetObject("Outlook.Application")
> > set NS = myOutApp.GetNamespace("MAPI")
> >
> > Using GetObject will allow you to use an existing instance of Outlook,
if
> > there is one; otherwise it will create a new instance. If you prefer to
> > create a new instance anyway, change the first line to:
> > set myOutApp = new Outlook.Application
> >
> > Hope this helps!
> >
> > Shadhi
> >
> > "Lee" wrote:
> >
> > > Can anyone point me in the direction as to why the following fails?
> > >
> > > Set NS = Outlook.Application.GetNamespace("MAPI")
> > >
> > > It is done on a server that only has outlook and exel installed (Excel
is
> > > the full instlal, outlook is only partially).
> > > --
> > > -Lee