Thank you for your suggestion of using exposed properties to solve my problem. Unfortunately, exposing properties that would be accessed by FoxPro would result in too many calls to the server (the original function has 11 arguments) slowing things down considerably. I have attempted to send the information back to the FoxPro container through a custom event in the control but the fire event function never seems to get called. First, is this a reasonable way to approach the problem without exposing properties? Second, why is the fire event not being called on the FoxPro container even though I do "fire" the event on the ActiveX control side? Also, do you know if FoxPro6 allows for the modification of function arguments?

Thanks again for your help.