Edward,

>Declare Function FPInitialize% Lib "ETFAXD32.DLL" (lpdFaxHandle&)
>DECLARE INTEGER FPInitialize IN ETFAXD32 AS FpInitialize ;
> Long @nFpHandle
>
>nStatus = FpInitialize(@nFaxHandle)

Not sure why the docs look like that. The & should mean Long value
but that doesn't mean the parm is by reference (although that seems
to make sense). Could it be that the result value is the handle???

Some DLLs that are designed explicitly for use in VB don't work with VFP.
VFP can only call DLLs that use Win32API calling convention (FAR PASCAL)
while VB specific DLLs use a VB specific format of pushing values
onto the stack (to minimize overhead).

If the docs don't point out a C example, I would guess that's what might
be the case.

+++ Rick ---