Geoff,

If you added it to your VB project through the References menu option then it's not an ActiveX control per se. In this case it would be a regular COM DLL which would have a ProgID that you can use with CreateObject().

If you don't have this info or VB sample code you can do a registry search for the GUID that you included below and look for the Key/Value of its "version independent progid" to use for your CreateObject() call.

If in fact it is an ActiveX then it could be one of those that don't play well in VFP. In which case all I can say is good luck.

>That is exactly my point. I cant seem to do either. I have tried adding the DLL to the list both in the tools and in the Insert Control dialog with no success.
>
>Yet when I use VB.net and add a reference to the project my ActiveX is there. I am pretty unfamiliar with VB so I have not got much further. Another thing I noticed on the VB side is that the COM Reference list is much bigger than the list one gets within VFP.
>
>Why is this?
>
>Once I have added the refernce to my VB project I can see the class ID (or Identity as it is called in VB)
>
>

{8B79962D-6444-4B64-81B3-BB9711C86B4E}\3.1\0\tlbimp

>
>and VB refers to the reference as being of type ActiveX
>
>I can also use the VFP Object browser to load and view the classes, their properties & methods within the DLL. It displays the following info
>
>

Library XenoNet6000
>File: C:\PROGRAM FILES\XENONET6000\XENONET6000.DLL
>Help File: This library doesn't have an associated help file.
>GUID: {8B79962D-6444-4B64-81B3-BB9711C86B4E}

>
>This is the second DLL/ActiveX/COM object that I have been unable to access via VFP yet others using VB can access it. Obviously, there is something missing somewhere that VFP needs before it can load/create the object and there is clearly some difference between VB and VFP.
>
>The question is what is that difference or to put it another way what do I have to do to be able to create my ADO object?
>
>>Hi Geoff,
>>
>>Registered ActiveX control should appear in list of ActiveX controls (Tools->Options->Controls). After checking this control should appear in controls toolbar (when it switched to ActiveX controls mode). Please take into account that controls in list are sorted in case-sensitive order. If control is still not in list, then you can press "Add..." button and select required ocx file.
>>If you have a simple COM object (not a control), then just create this object in code:
>>obj = CreateObject("SomeLibrary.SomeObject")
>>In this case it not required to add the reference to object in VFP.
>>
>>>I have a (ADO) com object which has been supplied to me for interfacing purposes.
>>>
>>>I ran their install program and also used regsvr32 on the .dll
>>>
>>>When I try and add the object in the form designer it is not there. When I go into visual studio.net and add the reference it is.
>>>
>>>What is the difference between VB and VFP???
>>>How do I make the COM object visible to VFP???