|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#1
December 5th, 2006, 04:29 AM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
Getting the structure right from the start
I want to be able to compare plan vs actual for this year and years past in a
sales database. Should all of this be in one table or should I put each year in a separate table. If I put each year is a separate table how do I then compare result by month for plan vs actual year or year? 
|
|
#2
December 5th, 2006, 05:09 AM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Getting the structure right from the start
On Mon, 4 Dec 2006 20:29:00 -0800, John Pierce
wrote: I want to be able to compare plan vs actual for this year and years past in a sales database. Should all of this be in one table or should I put each year in a separate table. If I put each year is a separate table how do I then compare result by month for plan vs actual year or year? Certainly in one table - or perhaps two, one for plan and one for actual. Storing data in tablenames (or fieldnames) is a Very Bad Idea. Just have a Date/Time field containing the sale date; you can use Queries to filter, sum, group by, etc. the year, or month or quarter or week, as needed. John W. Vinson[MVP]
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
