Rob Kennedy wrote: <...You can load the DLL with LoadLibrary, and directly call a function that creates an instance of your class and returns an interface reference for it.>
Rob, Thanks for your reply. What I didn't tell is, that part of the functionality of the DLL is also used to facilitate communication with other applications with Automation and that's the reason we used Automation to implement the whole thing. The only issue here is that the extra interface I created as part of my bugfix is only relevant to the Delphi app and the DLL and in that context I want to know whether the interface should be registered. In the meantime I tested it on a machine without a privileged account and it works, even without registration. But, I still wonder what COM uses the interface registrations for, if there is a TLB. After all, the TLB tells all there is to know about CoClasses and the interfaces they support. Greetings, Peter Laman Senior Software Engineer Lance ICT Group Roermond, the Netherlands http://www.lance-safety.com __________________________________________________ Delphi-Talk mailing list -> Delphi-Talk@elists.org http://www.elists.org/mailman/listinfo/delphi-talk
