Paul,

Then you should look at the relationships between the tables, if there's some set of functionality that a group of tables provides then you might use that to determine what classlibs to segregate the classes into. It would also help to think in terms of reusability across several apps.

>>You should have at a minimum an abizness.vcx or similar class library that holds all your business object classes. The general rule is one business object (class not class library) for each updateable table.
>>
>
>Good! That is what I did (lbizness.vcx).