>>>>Hi,
>>>>
>>>>I am always looking for better way to organize the libraries of my project. And now I am thinking of a better way to keep BIZ objects. I have a BIZ object for each table of the application (approximately 80 tables). I am thinking that a better way would be to have a separate .VCX library file for each BIZ object. But then I would end up having approximately 80 more .VCX files in my project. What are the downsides (if any) of having so many .VCX files in the project?
>>>>
>>>>TIA.
>>>
>>>The project is a representation of the .exe There is no harm in having tons of files in the exe. I have most of my functions as separate .PRGs. I probably use more vcxs than most because I aim for one class per vcx, just as I aim for one screen per scx. Since I know the name of the one I want most of the time, I get immediately to it, just by typing modify class theclassname of theclassname.vcx
>>>
>>>I can work with the project manager because of naming conventions. There isn't really any downside at runtime. At design time, if the component gallery/object browser was better, then I could categorize my stuff better. By categorization, I mean something like assigning tags to functions/classes to increase the likelihood of finding the one or ones I seek. Categorizing by physically placing things in vcx/prg, arbitrarily does not work. Virtual categorization is necessary.
>>
>>Thank you very much. This is helpful as I also know very well all the names in my project and separating each BIZ into its own classlib would be helpful for project maintenance. Although I don't understand what you mean by "virtual categorization."
>
>I have a bunch of business objects. Members, Addresses. I put them in one UE.VCX. Now I have to remember to look in UE.VCX to find them. In a way they are physically categorized as UE business objects. What I want is a way to "tag" each class. The tags would be, UE, Members, Addresses, Bizobj, Business Objects, Houses, Mailing, People, etc. They are keywords linked to the class. If there was a hierarchy of tags, and/or a search utility, I could categorize the components in many helpful ways. You could tag them with your own keywords which would help you find them too.
>
>Physically grouping them into a VCX does nothing at run time and is far from efficient at design time.

Thank you for sharing the information.