I think that mayby better solution is to use parameter tcTableName to indicate what class should be generated/regenerated. Maybe what we need is two optional parameters tcTableName,tcClassLib. Using such parameters invoking CA bulider several times would produce requeired set of classes in choosen VCX library . For me placing by default all CA clasess in one VCX is good idea (like other things you did in CA builder) - essentially it is enough - I always can drag and drop produced classes to another VCX library.
Thanks for including comments in CAbuilder. They will be helpfull not only to me I think.


>That would be quite easy enough. Thanks for the idea. Use discretion options are good since it they who take responsibility for the results, e.g. dozens, hundreds, thousands of VCX/VCT files. < g >
>
>>Then as an ER, consider having it make a VCX for each. If I want to share one between multiple apps, it would be easier if they were already broken out. In some COM stuff I did, one VCX brought it all kinds of stuff that I didn't need.