Novice
Windows XP 
Access 2003
I have data for a company having several divisions and I could just create one table. However, since most queries will pertain to data within one division it would therefore seem (to me) to be faster to have one table per division. But then how do I handle a query pertaining to the entire company? So should I just use one table (and take the performance hit), or learn to combine/merge/join/whatever the individual division tables for company-wide queries?
Last edited by gmetze; 01-28-2012 at 09:49 AM. Reason: be more explicit
Who is John Galt?
Windows XP Access 2007
I would use one table, which is the normalized design anyway. Even if there's a performance hit, it would be less than the grief of dealing with multiple tables.
Novice
Windows XP Access 2003
A single table it will be then. Thanks.
Gerry
Who is John Galt?
Windows XP Access 2007
Combining first and last name
Posting Permissions
Reply With Quote