I knew I was forgetting something... decorated names!
Thanks for remainding me,
m.

> Marco,
> 
> Cardyn is more correct.  Just because it's a DLL doesn't mean you can 
call
> functions from it with VB.  The DLL MUST export the function, and without
> C++ name mangling.  This means that the function must be declared with
> WINAPI, _stdcall or _cdecl and be in an "extern C" export.
> 
> While many DLLs do follow this convention, many do not.  A good test is 
to
> get the file's header and try calling it.  Again, inclusion in the header
> doesn't necessarily mean it is available, and omission doesn't 
necessarily
> mean it isn't there.