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