Best practices

Hi folks,

I inherited the development of a 3 tier application that have: VB Client, Intranet, Oracle and VB COM+
Above are the problems that I found:
- The source code on some components wasn't equal to the compiled components on production server. (Solved)
- There are 180 components for 90 entities (1 business component and 1 data component for each entity)
- Some of these components wasn't optimized for performance: Stay on memory, unattended execution (Solved)
- Some of these components doesn't have binary version compatibility with previous versions of the same component.
- The references between components are early bound. Example: One business component references 3 data components via the References menu, not whith CreateObject

I think that I can change some things on this scenario and want to know what other programmers think about it:
- I'm thinking in join all these 180 components on only one component. I will gain on memory usage and performance, not?
- With only one component with all the entities I will not have problems with binary compatibility, if I take care of it on this component.
- With this change I will not reference any other component via early bound and will not have problems with dependencies.
- I will call the classes from the component to himself with CreateObject. (Recursion)
- With these changes the execution of the components will be a lot of simultaneous connections to the same component instead of few connections to a lot of components, but the total connections will be the same. Will this affect the performance? Will be better or worst?

Please put any thoughts or suggestions to these questions, will be very glad. I need to have a sollution to this scenario on tuesday! (arrgh)

Thanks,

Fernando J.B. Cardoso