Companies, Title Companies, Real Estate Offices, Suppliers

[Christopher Glaeser]

We have four types of companies in our (to be implemented) database, which
are Title Companies, Real Estate Companies, Suppliers, and all others. Some
of the drop down lists in some of the forms should be limited to one type of
company (e.g. Title Companies). I see at least two alterantives when
designing the tables:

1. Create four tables, one for each type of company.

2. Create one table for all companies, and add one field that specifies the
company type.

I'm just beginning and know how to implement design 1, but I'm guessing
design 2 might be the better approach. Is that correct? Regarding the drop
down lists in design 2, how is the drop down list limited to the subset of
companies that are applicable for that field?

I'll have this same issue regarding contacts. There are escrow agents, real
estate agents, and everyone else. Again, I'm assuming one table for all
contacts is the preferred solution, and a drop down list for escrow agents
is selected for a query or some other technique. Any suggestions or
pointers will be greatly appreciated.

Best,
Christopher

 

[John Vinson]

We have four types of companies in our (to be implemented) database, which
are Title Companies, Real Estate Companies, Suppliers, and all others. Some
of the drop down lists in some of the forms should be limited to one type of
company (e.g. Title Companies). I see at least two alterantives when
designing the tables:

1. Create four tables, one for each type of company.

2. Create one table for all companies, and add one field that specifies the
company type.

I'm just beginning and know how to implement design 1, but I'm guessing
design 2 might be the better approach. Is that correct? Regarding the drop
down lists in design 2, how is the drop down list limited to the subset of
companies that are applicable for that field?

I'd absolutely agree. Simply base the Combo Box on your form (NOT in
your table - table datasheets should not be used for ANYTHING other
than debugging, and tables should never contain combo boxes!!!!) on an
appropriate Query. If you put a nonunique index on the company type
field you'll never notice the performance hit.

I'll have this same issue regarding contacts. There are escrow agents, real
estate agents, and everyone else. Again, I'm assuming one table for all
contacts is the preferred solution, and a drop down list for escrow agents
is selected for a query or some other technique. Any suggestions or
pointers will be greatly appreciated.

Ditto.

 

[Randy]

Design number two is most defintely the better way to go,
it will give you much more flexibilty in the future for
queries and reports, besides the fact that it is much
easier to manage just one table.
As far as the second question, if I am understanding it
correctly you want to have a pull down menu inside a
table? If so you can use a lookup and most likely go
ahead and create a query that gives you the available
choices for that record. that is of course if i am
undertanding what you wanted

Randy

 

[Christopher Glaeser]

Design number two is most defintely the better way to go,

it will give you much more flexibilty in the future for
queries and reports, besides the fact that it is much
easier to manage just one table.
Thanks!

As far as the second question, if I am understanding it
correctly you want to have a pull down menu inside a
table? If so you can use a lookup and most likely go
ahead and create a query that gives you the available
choices for that record. that is of course if i am
undertanding what you wanted

The second question was pretty much identical to the first. Rather than
several types of companies, question 2 was several types of contacts. Based
on your response above, I'm guessing one contact table is preferred to
several contact tables.

Thanks again!

Best,
Christopher

 

[Christopher Glaeser]

I'd absolutely agree. Simply base the Combo Box on your form

Thanks!!! Makes perfect sense.

Best,
Christopher