It's ok to break the compatibilty when you create a new object.
Breaking the compatibilty means VB creates a new GUID for this object. The only problem with that is, each time you break it, the user has to re-register the component.
So, this is the reason why you usually set the compatibility to the DLL once it's created.



LinkBack URL
About LinkBacks





Every time I change the name, it breaks compatability or something.
Reply With Quote

Bookmarks