Providing selective access to a VB 6.0 ActiveX DLL
Posted on 2004-11-09
I have an ActiveX DLL that I want to distribute with my application, but I don't want people to be able to use its exposed (public) methods. Is there a way I can determine from within the ActiveX DLL which Windows program called it, and if the calling program is one of my programs to allow the call but to disregard it otherwise?
I thought about having my programs just send a secret code to activate the DLL. Problem is someone could just use my program to activate it, and then make calls to the DLL themselves if I don't have a way of detecting which program is making each individual call.
Thanks for any suggestions!