🚀 go-pugleaf

From the last conversations I had with MS, CDO was not redistributable as of
then (about 2 months ago).  Bit me bad since I thought it was the best thing
next to sliced bread (at first).  It also has some problems running on WinNT
4.0 with the SMTP protocol.  GPF's everytime the session loses scope, either
by an explicit Set = Nothing or the procedure terminates.

Later,
Tony Fountain, MCP
tonyfo at primenet dot com
ICQ# 16575458
Please do not email me directly, my wife already clutters up my inbox

Surfer <DontReply@ThisAddress.net> wrote in message
news:#TvOv8kk#GA.285@cppssbbsa02.microsoft.com...
> You should switch to CDO instead. It is completely COM compliant and can
be
> used without any "Declare" within VB.
> Furthermore, it is feature complete which means you can do anything you
want
> when messaging is concerned.
>
>
> XYZ <vanluc@faltec.com> wrote in message
> news:A34V2.137$gi2.17742@wagner.videotron.net...
> > Why is it that VB doesn't recognize this:
> >
> > Declare Function MAPISendMail Lib "MAPI.DLL" Alias "BMAPISendMail" _
> >    (ByVal Session&, ByVal UIParam&, Message As MAPIMessage, Recipient _
> >    As MapiRecip, File As MapiFile, ByVal Flags&, ByVal Reserved&) As
Long
> >
> > if i declare another function from, for example kernel32, no problems!
The
> > problem appears when i try to use mapi.dll or mapi32.dll...TIA!
> >
> >
> > --
> > Good day to you!
> > www.illusion.qc.ca
> >
> >
>
>