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.

 
Go Back  dBforums > PC based Database Applications > Microsoft Access > How to Design This DB

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 07-14-11, 10:20
dlester dlester is offline
Registered User
 
Join Date: Jul 2011
Posts: 11
How to Design This DB

Hi All,

I am working on a database where the sole purpose will be to enter numbers given to a District Manager by the regional managers to track their numbers by quarter. They want the DB to retain the data each quarter, but start clean the next quarter. So basically they want to be able to archive each quarter's data, and start fresh each new quarter. I'm scratching my head a bit, because I know how to design the DB assuming they didn't need to retain the previous data. I've designed some Access DBs before, and was Microsoft Certified in Access 2000, but I've become a bit rusty.

Thanks!
Reply With Quote
  #2 (permalink)  
Old 07-14-11, 12:21
healdem healdem is offline
Jaded Developer
 
Join Date: Nov 2004
Location: out on a limb
Posts: 9,250
why archive stuff off
'just' define what the time periods are
stuff the data into wahtever table(s) you require
then extract the data as required
given a good enough design then you can also run compratives against other time periods


eg this quarter 2011 against last quarter 2011, this quarter 2011, this quarter 2010 and so on

flushing the data doesn't make sense unless you have some other problem such as available storage space
__________________
I'd rather be riding my Versys or my Tiger 800 let alone the Norton
Reply With Quote
  #3 (permalink)  
Old 07-14-11, 16:47
dlester dlester is offline
Registered User
 
Join Date: Jul 2011
Posts: 11
Quote:
Originally Posted by healdem View Post
why archive stuff off
'just' define what the time periods are
stuff the data into wahtever table(s) you require
then extract the data as required
given a good enough design then you can also run compratives against other time periods


eg this quarter 2011 against last quarter 2011, this quarter 2011, this quarter 2010 and so on

flushing the data doesn't make sense unless you have some other problem such as available storage space
Ok so are you saying make a table for each quarter or am I missing something?
Reply With Quote
  #4 (permalink)  
Old 07-15-11, 04:42
healdem healdem is offline
Jaded Developer
 
Join Date: Nov 2004
Location: out on a limb
Posts: 9,250
Quote:
Originally Posted by dlester View Post
Ok so are you saying make a table for each quarter or am I missing something?
No, and yes you probably are missing something:-
have one table for all your sales data
define a table elsewhere which describes the periodic element (eg quarters)

then extract the data as required according to the periodic table

at a guess I think you'd be better off defining financial months, rather than quarters (or as well as quarters) so you can solve what ever periodic time series question your users are going to throw at you.
__________________
I'd rather be riding my Versys or my Tiger 800 let alone the Norton
Reply With Quote
Reply

Tags
access, design

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On