>>I have 2 VCXs. In each one, they have some classes defined which are based of of some parent class in the other VCX. So, it's kind of a tangled mess.
>>
>>At this point, I'd be happier if I could just merge them together into a single vcx. There are no conflicting names.
>>
>>I can work out changing all the vcx references on all the forms of my app, but I'm wondering if there is any magic I can use to cleanly merge the 2 vcxs together???
>
>Putting all your eggs in one basket is not a good practice. Leave every class separated at design time - just like mother nature does. By that I mean, you can produce an artificial list all of the individual types of cells in the body. You can put the whole list on one page, but then it becomes troublesome to share with others. You can even have the items in the list reference a list of stem cells - to show hierarchy. That is the right way to organize classes.
>
>Don't confuse the classes and vcxs with the actual cells - which only exist at runtime. We are designers working with blueprints.



>>Leave every class separated at design time - just like mother nature does.

There were 60 classes in one vcx and 30 in another.

Are you saying each class should have lived in its own vcx? Not for me.

I have one app, and the classes had become all mixed up between the 2 vcxs by me being sloppy over time. I was tired of hunting down which one lived where. So, for me, I was happy enough to combine them all together.



>>... it becomes troublesome to share with others.

Thanks for the compliment, but believe me... no one else wants any of my crap code in their app. I've never needed to share by textbox class or combo class with anyone else for 20 years, so at this point, I'm going to say that's a non issue for me. I prefer the one-classlib appraoch.