We will try this again..


>The VFP servers have been fully debugged and tested within VFP (using
>CREATEOBJECT from the command window) and seem to work fine.

This is not an accurate way to test your automation servers. It would be better to instance them in something other than VFP - like Excel, VB, or in a client-side script in IE. I have seen where VFP treats servers it creates differently in its (VFP that is) context than in something else.


Is the DLL created actually in the MTS package? Once again, I think you are going to run into problems because of the compatibility issues between MTS and VFP 5.

FWIW, in the context of DLL's, I would guess SYS(3050) is applicable. If the application that instances the DLL is in the foreground, since the DLL runs in the same process space, my guess is that VFP is also part of the foreground. I could be wrong here since I have never tested it. In any case, it is something worth investigating.

In your DLL, I would suggest setting SYS(3050,1) and SYS(3050,2) to different values to see what happens. The FoxTalk article should be a good guide.

Often, there is no science to any of this - it is trial and error.

Good luck