DataModules General Question On Usage

[Knipfty]

I'm guessing there is no right or wrong answer her but I'll give it a try.

I'm building app with about a dozen tables and about as many Edit/Entry forms.  Usually there is DBGrid based form that leads to an edit/entry form bia menu clicks.  Right now, I've all the Tables, Queries, and datasources to be local to each form.

I'm thinking of moving these DB Access components to a DataModule or perhaps multiple DMs.  What is a good practice?  One DM for the entire app or one for each form or something in between?  If I go with just one DM for the enitre app, do I add DB components to be shared where possible or simply map them to each form and keep adding them as I add more forms?

Thanks

Knipfty

[taazz]

I always use one DM for each logical unit eg Customers. This way I create the datamodules and their forms as the end users selects them to be displayed avoiding to have all that data and objects in memory. Also you must keep in mind that in some cases some master/detail relationships must be re-defined for each unit avoiding conflicts between the various units them self eg selecting a customer phone type and the active employe phone type changes too.
also you must keep in mind that it would make it a bit difficult to use dataset events (eg onscroll) to refresh objects in the grid or edit form.