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.

>It creates 1 VCX that has a CA baseclass then there is 1 CA subclass created for EACH table with the CA baseclass as the parent.
>
>>Hey Mark
>>
>>Does it make one VCX or a set of them?