calldll vs calldll32

[don lowenstein]

I'm having varied results using dll and dll32 processing with FWH 7.09 and xharbour 99.71

- gpf's are occuring under various circumstances. Using xharour 99.5 - no problem.

question - what's the reason I would choose calldd or calldll32 for dynamically calling an external dll.

Aren't all dll's 32-bits these days?

My mystery is, if I use getprocaddress(), loadlibrary(), freelibrary(), calldll() I have successful results with xharbour 99.51 and fwh 2006

using xharbour 99.71 and fwh 7.09, gpf occurs with getproc32() and I never get to the calldll32.

If I use the "old" calldll conventions, most calls work in 99.71 but not all - this was not a problem with 99.51.

If I use the calldll32 conventions, I get gpf on getproc32()

Anybody else having varied results in calling dll's between these versions of fivewin and xharbour?

[Antonio Linares]

...32 functions names are for 16 bits only. They exist from FW 16 compatibility. You should use the functions without the ...32 suffix.

The only difference regarding those functions is that previously the DLL was kept opened by mistake, and now it is properly closed. Some DLLs require to kept opened meanwhile you are using them, from one call to another.

The way to solve it is to previously load the DLL:

local hDLL := LoadLibrary( <cDLLName.dll> )

... make your DLL functions calls ...

FreeLibrary( hDLL )

Please try it this way and you should not get any GPF at all, thanks