>>Terry,
>>
>>I too have lots of trouble reading VFP documentation, even when I actually find (or come across) something I am looking for!
>>
>>I *suspect* in this case that the reference is to a "user Interface" on the server **FOR** the server - that is, the operator AT THE SERVER only.
>>
>>But who knows? @!#@!
>>
>>Good luck,
>>
>>Jim N
>>
>
>Hi Jim,
>
> You may be correct, but I hope not. A user interface at the server would do me no good at all ... that is, unless each of the clients are all located at the server!
>
>Thanks,
>
>TFISHER

Terry, what you're trying to do by including a GUI interface in an OLE Automation Server is to create a complex control, something that VFP can't do (there are lots of reasons why, and this is one place where VB and VJ++ have a tremendous advantage over VFP; they can create an in-process server that can interact with the application's event loop, creating a control.) I've not seen a control that was not an in-process server (.DLL) at its core; if it interacted with an out-of-process server, the control and the automation server were distinct items, each with their own ProgID and OLE Interface.

Create your mid-tier object with VFP, and if you need to insert a GUI into another application, create a control that talks to your VFP server in another language.