🚀 go-pugleaf

"Bob Gonder" <notbg@notmindspring.invalid> wrote in message
news:57cqsv0oufvcav13m7c9b9v06dgn7e6cps@4ax.com...
> Dennis Jones wrote:

> Headers don't of them selves, cause the compiler/linker to bring in
> the needed libraries.  Other than the standard kernal libs, you need
> to add each addition library (not just the headers) your app requires.
>
> mapix.h defines MAPILogonEx as a function pointer. Somebody somewhere
> needs to fill in the pointer with the runtime address of the function.
> If you have a mapi32.lib, and have it linked with your app, then it
> should fill in that address when your app starts. OTOH, since it is an
> extended function, maybe the lib doesn't do that for that particular
> function, so you would need to do it yourself.
> It looks like MAPILogonEx is in mapi32.dll, so the above code should
> work.

I think you've misunderstood...I was referring to compiler errors, not
linker errors.

Anyway, I did a little more research.  It turns out that the simple MAPI
functions are built into Borland's VCL package.  However, the extended MAPI
functions are not.  This explains why I have never had trouble using the
simple MAPI functions (without resorting to LoadLibrary/GetProcAddress), and
why one might see compiler errors (as the OP did) when attempting to use
extended MAPI functions, such as MapiLogonEx.

Thus, the solution (for Fernando, if you're still reading this thread!) is
to use LoadLibrary and GetProcAddress as Bob showed in his first reply.

- Dennis