>>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.
>
>In my experience it is better to have "too many" vcx than too many classes in one VCX. Now when I look back into older projects where I have some of those "monster" vcx with more than 10 classes (some can have over 30 classes!) I really regret this.
>
>Because of the limitations of the VFP project manager (missing folder structure) the key is naming conventions. What I do it to group closeley related vcx together and to use the underscore to separate the names, just as you would use a folder structure:
>
>audit_actions.vcx
>audit_changes.vcx
>audit_interfaces.vcx
Thank you very much.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
