Yes, the linker can't find it. That's why it's a good idea to use a full path with LoadLibraryEx.St_W wrote:Means that the linker cannot find xlcall32.dll or that the file is invalid. Make sure you use 32-bit FreeBasic for loading a 32-bit DLL (and make sure that the DLL is actually a 32-bit DLL).jj2007 wrote:Method 1 chokes with "FreeBasic\bin\win32\ld.exe: cannot find -lxlcall32".
Your return value signals that you use an outdated (unsupported) version, maybe that's the problem and that version is buggy. My version returns 3072.
Your version is a bit newer, but that doesn't mean it's not "valid". FB cannot load it, because it uses only LoadLibrary. But LoadLibraryEx can load the library, and returns the version correctly.
Prints the address of the XLCallVer function, you've to use XLCallVer() to make it work. Still doesn't help if you're using a faulty DLL that cannot be loaded.
You can examine/check the DLL with the dumpbin tool.
Of course it prints the address, but since FB cannot load the library, the proc address is zero, so XLCallVer() will just produce an exception. And I have examined the DLL, of course, it is perfectly valid and works fine with LoadLibraryEx.