Why does VB6 append Ctl to my OCX library name
Visual Basic
1
Posts
1
Posters
0
Views
1
Watching
-
I have a VB project that contains a number of controls. The project is called Controls and one of the controls for example is called Label. So when used in another project the control type name is Controls.Label. Fair enough. I have reimplemented the Controls library containing the controls in ATL keeping all the original GUIDS, IIDs and names to maintain compatibility. But VB insists on appending Ctl to my name, making it 'ControlsCtl.Label'. This makes the orginal VB form fail to load. Any ideas?