>>>>The DLL does not show in the list and I think I know why. After hours of google searches I found a number of references to visibility of .NET components to non-.NET languages.
>>>>
>>>>These refer to the use of REGTLIBv12.exe and REGASM.EXE .
>>>>
>>>>I have .NET 4.5.1 installed and both programs are in the folder C:\Windows\Microsoft.NET\Framework\v4.0.30319\.
>>>>
>>>>Can you confirm that I need to run these on the .TLB and .DLL files and whether the order of running is significant?
>>>>
>>>>Thanks for your assistance
>>>
>>>Ah, .net -- a horse of another color, as it were.
>>>
>>>You will need something like wwdotnetbridge http://west-wind.com/wwDotnetBridge.aspx to use it in VFP, if it is a .net dll.
>>>
>>>Hank
>>
>>Not necessarily true. If it is a .NET library and has been registered for COM then it should work (although, admittedly, that might depend on the complexity of the methods and properties exposed).
>>
>>Anyway it occurs to me that if the library shows up in the VFP Object Browser then it is, de facto, in the registry as a COM object and thus should be available.
>>
>>Maybe the problem lies in dependencies of the library. It seems to be a Sage library so it may need Sage (or at least parts of it) installed ?
>
>He said it did not show up in the object browser: "The DLL does not show in the list..."

I think that was referring to the 'Insert Object' dialog.
It was shown in the Object browser ( see the JPG in the OP.....