i'm pretty sure fox registers them when you build them.
you should be able to run regsvr32.exe on the dll to register it or include it in a setup prog to register it.


>I am new to creating OLE servers. I am just getting started and I have a basic (I think) question. I created a test.DLL (and test.TBL & test.VBR) in VFP 5.0. I then did a CREATEOBJECT, etc. in VFP 3.0 and all worked well. My understanding is that when I created the .DLL, it was registered as an OLE server on my machine. Is this correct? If not, please explain. Also, how do I take the .DLL and register it on other machines (NT 4.0)?
>
>Thanks in advance,
>
>Joe
>
>>>>I also found that by searching the archive. Many people wanted to have that. I think what we are trying to do is to have an ActiveX look-a-like control and this won't be supported before Visual FoxPro 6.
>>>
>>>Actually, no. In VFP 6.0 Automation servers cannot have a visible interface at all...
>>>
>>>The only way that you can simulate a 'control' in 6.0 will be to build an ActiveDocument application,
>>>but VFP 6 will not support ActiveX control creation per se.
>>
>>Where did I hear that Visual FoxPro 6 will support ActiveX and ActiveX document?
>>
>>>>So, OLE server is what we have now. I thought we would have been able to add a class grid on a Visual Basic form to be able to benefit of the power of Visual FoxPro when come time to deal with big tables.
>>>
>>>You can, but you have to use EXE out of process servers to have UI...
>>
>>Yes, this is what we do now. However, it would be nice to incorporate a container in a Visual Basic form. At this point, I only found a way to have a form class top level.