I have two controls that I need to use in one project. They have different filenames but they have identical exported function structures. This means that VB cannot distinguish one from the other internally. The current resolution is two executables. (poor, I know.) My thought today is that if I could wrap those controls up in a vb dll of my own. Protecting VB from the fact that the internal structure is the same and letting my code make the determination as to which of these controls to use when. But I dont know how to impliment this solution. This is where I need some help.

If I am not being clear enough PLEASE let me know so I can explain better. I really need some help and I do not wish to be my own bottleneck. :)