>>no ideas here...except to echo that maybe the DLL not registered properly on your machine, or the DLL is not written properly
>
>Nope, VB DLLs, VFP DLLs, they're all the same: they don't export functions (except the four COM functions).
>
>Registration wouldn't have anything to do with exported functions anyway. If I write a DLL that exports functions, it's unlikely that I'll write code for DllRegisterServer(), which is the function needed to register a COM DLL, because I won't be using COM to give the desired functionality.

Hello Mike,

Well, I knew i shouldn't have answered his question (i was sucked in by the undertow), have only worked with DLLs via CREATEOBJECT(), except for the following case. I use third-party DLL that I was told was written in VB (by a salesperson?), and I get to it in VB via a DECLARE statement and function calls. Does this mean that particular DLL was written in something other than VB (probably C++)?