General information
Category:
COM/DCOM and OLE Automation
Hello,
you said that
x=100
activeX.Method(x)
does not trigger the error, so why not call it like that way?
does the activex alter the value passed or doesn't work properly?
maybe you could write a little wrapper fll in C and then call the methods which require such "strange" (in fox terms) parametertypes through it
i'll test this approach, writing a little ATL Object which expects a SHORT by reference and report my results later
Regards
Christian
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only