Advice on relational architecture/design before building

[Stephanie]

Hi all, I am interested in developing a datasbse for my company that allows
us to do the following:
import excel text files into different tables
4-5 tables to feed the master list of data colelction
pre-defined reports at the click of a button ulling trends, averages, sum,
of the data collected based on key words and fields.
allow for simple searches for non tech savvy people

Note: I cannot connect the forms for data collection to this, which is why I
need to import the excel files. I know I know... call is corporate CMS
limitations.

2 forms can be connected to this database and hosted in the same server
location.

So, any tips or things I should be thinking about before starting to build
my tables, etc? I haven't build a DB in a long time and just wanted to get a
sense of how the funcationalty has changed, or technical issues to be aware
of as I start this project.

Thanks!

 

[Klatuu]

As you move forward, asking specific questions will certainly get you the
help you need, but broad brush posts like this don't get much attention.

I don't understand this statement:
2 forms can be connected to this database and hosted in the same server
location.

 

[Fred]

Advice is to do these 4 steps:

1. Define your data storage mission and your functionality mission

2. Define the content, nature, organization and real world relationships of
the data to be stored

3. Define a table structure which will support accomplishment of your
missions.

4. Create other items (queries, forms, reports, code etc.) to accomplish
the required functionality.

And get help at each stage as needed, providing the relevant info. You
post had no info from #1, #2 or #3.

Hope that helps a little.

Fred