Fabio,

This is VFP 8 so I'm limited on the second parm for BINTOC. I tried Anatoliy's solution but that didn't work, either.

Is this problem so uncommon that no one has run into it before? I find that hard to believe.

Still plugging away.....suggestions welcome!

>>It's not a COM question, it's a DLL question.
>>
>>I have a DLL that's defined as:
>>
>>DECLARE integer foo IN 'foo.dll" double @value1, double @value2
>>
>>Notice that the parameters are by reference, so they must exist from the calling code.
>>
>>So I call it with:
>>
>>value1=0
>>value2=0
>>foo(@value1,@value2)
>>
>>The result is that value1 and value2 come back with a strange value such as 2.63E-308.
>>
>>I have no idea what's happening. I haven't done any DLL work in a while so I'm clueless. Any ideas? It's times like this I really miss Ed Rauh.
>
>John,
>are you sure what the function foo returns doubles with little-endian rule.
>Post:
>

>?0h+BINTOC(value1,"BR")
>