I wasn't sure when it makes the most sense to have a new data base? Is there a rule of thumb? I was developing a quoting data base and job overview layout in another data base and feel that both could be in the same data base rather than having lookups since they use a lot of the same information. I came to this conclusion because I was having to constantly use a relookup when I adjusted estimate numbers on that could be found on the overview data base.

Any thoughts?

-Morning Man

This is really a database structure issue. The most important question is always "What does a record represent". The answer might be a person, a contact, an inventory item, an invoice. As a general rule, you only want a single file for a given entity. You could, however, build a contact manager with one file for people and another file for addresses.

-bd