>Nancy/Erik,
>
>Interesting that your answers are at total extremes to each other.
>
>Erik, I assume that your class library for dataentry forms, for example, have only a few classes in it. IOW, your class doesn't contain all your forms, you limit it specifically to the type, dataentry. Correct? So then, you might have a library containing only dialog box forms, etc. and similar grouping for buttons libraries and other controls libraries.
>
>Nancy, I've considered grouping classes your way also, but wondered about redundancy. It reminds me of a discussion I had with a friend about this: there are several "types" of forms in his application. One for simple dataentry, one for forms with grids, one for dialog boxes,etc. Similar to Erik's method, each type of form would have it's own class library, but similar to your method, there would be specialized button classes and textbox classes in each of these form class libraries. Because a textbox would most likely have different properties/methods in a dataentry form than what it might have in a dialog box, for example. We never did decide which way was the "better" way of doing it, but I think he decided to build his libraries following Nancy's method.
>
>Anybody else have any comments on this???
>
>-Bonnie
>

---

Hello there!

Take my case as consideration!

I made 2 set of company Sales System Under the Same Company GROUP!
For me, I made 3 VCX for each system!

a) lovehome.vcx - High Level Class, Form and Formset
Most of the coding are designed for EACH seperated company, such as discount structure!
This VCX is Non-Reusable, but as seperated, no non-used form will put into another company VCX!!
==> As Erik said, the Execute File size is minimum at this case!
b) no_ime.vcx - Low Level Class, textbox, cmdbuttongrp, combox, lstbox, grid, container, timer, custom
Most of the reusable class are put here!
Such as OOP Her... parent-child textbox, grid group and container set..
At here, I suggest NOT to put the tightly related class, into different VCX!

   txt 
    +-- txtDate
    +-- txtNumber
    +-- txtEval

should put altogether!!
Some special coding, which I want to hide them will put as NEW procedure of custom class!!
c) testing.vcx - New testing Class, Just for testing and try! Excluded from project
Sometime, I download some vcx class from file section or
Just for try/test!!

Since in my cases, both company need all the cases in common base control,
there is no waste in my Class b).
Because I need to maintain both system in Different machine
I always copy the no_ime.vcx (common class) with me if need update!!
So, even I build a new project, I save time to build the base low level classes!

Of cos, if there are many projects to do, Barbara suggestion is also good!
Group the class in same for similiar Functionality!
Then pick up the needed vcx is enough!

What I mention is:
If you change the Class in classloc, remember to check it Especially you build 2 or more
project in same machine

Because there may NOT have problem on compile the execute file as you have both vcx in
machine but you don't have those vcx on other directory in client PC when RUN!!

To check it, hack the vcx:

Use myClass.vcx
Set Filter to [:\] $ Classloc
Browse && to see any class in different directory!!

Even you divide classes into different VCX files, most likely they are in same directory!
Thus, the above coding can check any missing Class Location!

2nd check, sometimes is the ICON, picture path!

Use myClass.vcx
Set Filter to [:\] $ Properties
Browse && to see any ICON in different directory which is missing!!!

After the above checking, there will be no problem on disturb execute to client for
missing VCX, Class cases!

^_~ Good LUCK!