Is there a difference?

Is there really a difference of approach?

I have several things to consider in an estimating database. Production, Shipping, Field Work, Field Hardware, etc...

All of the above have account numbers. Now I was wondering, would there be any benifit to having one table or several tables?

One Table Example

Account (PK) | Category | Description

or

Multiple tables

tbProduction
Account (PK) | Description

tbShipping
Account (PK) | Description

tbProducts
Account (PK) | Description
etc....

I like having the tables split up and/or all in one.

Any thoughts, pros / cons?

Mike BIn the one table version, it could be easier to check for duplicate Accounts. The downside is that a user directly accessing the table needs to know about the category (and consider). Besides that, you may want to consider how access to the table(s) is arranged from a security point of view, eventhough both the single table / multiple tables have their own solutions. Next; in future, would there be any other categories to consider?|||In the one table version, it could be easier to check for duplicate Accounts.

Good point

The downside is that a user directly accessing the table needs to know about the category (and consider).

The reason for my questioning.

Besides that, you may want to consider how access to the table(s) is arranged from a security point of view

Basically they are simply lookup tables for the account numbers, so read only for most users and read write for a small group.

When I say look up, in shipping for example you can have three accounts, Trailer Rentals, Services, and Cost Overrun.

Next; in future, would there be any other categories to consider? [/SIZE]

Good point, but if there are, it would probably need further modification to the database and application so adding another table would not make a difference since the only reason I see doing this would be to change the scope of the "estimate".

Mike B