>Hi Ed,
>
>>if your DECLARE...DLL has a STRING @ parameter, passing an integer 0 works as a null pointer (equivalent to VB's vbNull construct.)
>
>I usually pass .NULL. in this case, VFP translates that to 0, as well.
>
>>a SHORT, which is two bytes, and can only be declared as the return type.
>
>That's new to me. I used it as a parameter type in DECLARE and it worked, except for passing by reference in VFP 5, where the return value is always 0.
>

That's what appears in the VFP6 docs; take a look at the current entry for DECLARE...DLL there; it lists available return types of SHORT, INTEGER, SINGLE, DOUBLE LONG and STRING, but only INTEGER, SINGLE, DOUBLE, LONG and STRING for parameter types.

>Christof