Among the different COM details that VB hides to the programmers, one of the most problematic one is that it doesn’t let you take control on interface GUIDs. Binary compatibility settings in VB try to make you follow COM rules (as a fact breaking such rules with the interface forward mechanism it silently implements when you add a method to a class). In any case VB support in Interface definition and maintenance is definitely lacking when you have to design and implement large COM based systems.

Here are a couple of links to articles that illustrate a technique that lets overcome such limits. This approach may be scaring at first to VB programmers that are not that familiar with C language, cause you have to go a little deep into IDL, nevertheless, trust me, that, after the first little drop of you development speed, you will get much more robust and well designed applications.

msdn.microsoft.com/library/techart/msdn_bldvbcom.htm
www.microsoft.com/msj/0100/versioning/versioning.asp

However, instead of using OleViewer to reverse-engineer the Type library I suggest you to use the TypeLibrary Viewer from www.vivid-creations.com/ because OleViewer does not always generate IDL that can be immediately compiled by MIDL to generate the type library without a certain number of adjustments. I verified that the tool I suggest generates ready-to-compile IDL.