> Is there a way to get the local filesystem path to a file that was just
> attached?
> I'm using Outlook 2000 and 2002 on 98, Me, 2000,XPh,XPp

> There seems to be Outlook object model support and EMAPI property hooks
for
> getting the path of an attachment, but all I ever see is the simple,
> pathless, filename.

> I just want to catch the AttachmentAdd event, and query the added
> attachment's .FileName and .PathName properties, so I can go work with the
> file in the local filesystem.

> Unfortunately, it looks like .PathName is documented only to be valid if
you
> attach a link to a file, rather than the file itself...and the pathname
then
> points to the linked file, not the attachment (the link file) itself.
(And
> .LNKs don't work very well nowadays, anyway, what with machine-name
> transposition and security patches.)

> Thanks,
>     -Dan Haygood

> Once you've added the attachment, Outlook apparently doesn't know or care
> where the attachment came from.

> --
> Sue Mosher, Outlook MVP
>    Outlook and Exchange Solutions
>    at http://www.slipstick.com

> > Is there a way to get the local filesystem path to a file that was just
> > attached?
> > I'm using Outlook 2000 and 2002 on 98, Me, 2000,XPh,XPp

> > There seems to be Outlook object model support and EMAPI property hooks
> for
> > getting the path of an attachment, but all I ever see is the simple,
> > pathless, filename.

> > I just want to catch the AttachmentAdd event, and query the added
> > attachment's .FileName and .PathName properties, so I can go work with
the
> > file in the local filesystem.

> > Unfortunately, it looks like .PathName is documented only to be valid if
> you
> > attach a link to a file, rather than the file itself...and the pathname
> then
> > points to the linked file, not the attachment (the link file) itself.
> (And
> > .LNKs don't work very well nowadays, anyway, what with machine-name
> > transposition and security patches.)

> > Thanks,
> >     -Dan Haygood