Help designing a db from many source dbs

M

Maarkr

I need to build a db where I will get information from about twenty different
access and excel sources on a network. These sources are updated at various
freqs, from hourly to daily to monthly.
The desired result is to 1) send custom weekly reports to different agencies
from queries that the user can select from these many sources 2) write this
information in a separate single db for review, reporting and archiving (need
to run a monthly and annual summary for a history archive hardcopy; I
believe a new archive db is necessary since the data sources may change,
links may drop on the network, or data reporting programs may change).
I was thinking of having linked tables from all sources in my db, and
running a weekly query to append a data summary from all sources into a main
table where I can setup many queries that the user can pick to put selected
information in an editable report.
Should I set up a flat file table with all info (maybe 150 fields) by week?
or would you have a relational db by date or source? This is an unusual db
duild for me. Thanks for any advice.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top