Hugo, it's actually a property. However, I found it strange too, because it appears to be a property that accepts parameters. Hence:

TColumnOn(1,1,ASIResult) = .T.

? TColumnOn(1,1,ASIResult)

>Joe,
>
>Is not clear to me if you are talking about a property or a method, for what I understood TColumnOn seems to be a method, so you can not assign a value to a method, but also you can not pass a parameter to a property (by value or by reference), so there are mixed concepts here.
>
>
>
>>I'm using a third-party out of process server. I highly doubt it was written in VFP, if that matters.
>>
>>For the most part, I can easily access the methods and properties of the exe. However, I'm stumped when I attempt to set one particular property. The documentation states that I should pass three variables: two integers, and then an integer variable by reference. Not only do I pass these, but the property is boolean, so I specify .T. or .F.
>>
>>All of this works fine in VB.
>>
>>

>>ASI916.TColumnOn(1, 1, AsiRESULT) = True
>>

>>
>>After issuing that command, the TColumnOn property is set to true. However, when I attempt to do the same in FoxPro, I have issues.
>>
>>If I try this, I get a syntax error:
>>

>>AsiResults = 0
>>ASI916.TColumnOn(1,1,@AsiResults) = .T.
>>

>>
>>
>>If I try this, I get an "Invalid Subscript Reference":
>>

>>AsiResults = 0
>>ASI916.TColumnOn(1,1,AsiResults) = .T.
>>

>>
>>Do FoxPro have an issue with passing variables by reference to an out of process server?