Massive Data Bits Against Timeline of Events

[Armorica]

Happy Hump Day yall! =)

I'm sure what I'm envisioning has been done a blue zillion times before, but I'm hoping someone here can help identify some best practices or otherwise preferred methods of approaching this need. I'm also sure that, as with most all new ideas, I'm likely horrendously overthinking this, and the overwhelming volume of results returned from my searches for the "already tried and true" is likely unnecessarily feeding that nasty habit of mine =)

What I'm going for is really pretty simple when I stop to make myself describe it in English. I deal with mass amounts of data reported at the national, regional, state, county, city, ZCTA, etc. etc. level, most data elements being monthly, but some being weekly, yearly, etc. Most data is relevant to the past thirty years, but some elements go back as early as 1770.

What I'd like to do is maintain another table of dated events, which of course can be incorporated into reports that allow for the presentation of data trends and their correlations, if any, to various events along a timeline.

Though I'm an advocate of "reinventing the wheel" when time permits and the benefit of the lessons learned and experience gained outweighs the "waste" of redundancy, I seem to be in amazingly counterproductive OCD sorts this week and would love to know "there's an app for that!" (templates, etc. etc.) that forces me to make this simple creation simple =) But if I'm among "teach a gal to fish" folks this morning, I'd be tickled just to have some great advice and maybe some direction that would help me narrow my search scope. Its not that I can't figure out how it can be done (I'm certainly no Access expert, but I'm a bit riper than green), I'm just predicting jumping in there and finding too many ways for it to be done, which will be compounded by my reformatting the same things 6 dozen ways until I settle on how I formatted it the first time (hehe), and ultimately wasting a ridiculous amount of time building a mousetrap that is not likely to be better than any of what I'm sure are many already out there.

Hehehe, just another Wino Wednesday, eh? =) Thanx in advance for bein kind to the neurotic!

[rpeare]

um... what is the question exactly? how do you store a 'dated' table? What do you mean by that, if it's all the same (relatively) data why would you need another table to store it. You can store it all in one table but mark the item with an indicator that marks it as weekly, yearly, monthly etc.