Re: Don't hate the rookie....please help -- simple question
- From: John Vinson <jvinson@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 29 Apr 2005 00:38:52 -0600
On Thu, 28 Apr 2005 15:36:01 -0700, "Erik"
<Erik@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>I would like to design a database which helps me track some stock information
>which builds daily. I have an Excel file with 500 stock tickers (fixed) and
>dates at top of columns. What is the best way to represent this data? I need
>to calculate and report % change in the Wk EPS values. Do I build a table
>for each date? Or each Ticker? Each day the data will increase and I would
>like to notice trends (i.e. one week or one moth trends). I have read the
>database design documents and help file to no avail...Thank you in advance.
>
>Sample:
> 4/22/05 4/25/2005 4/26/2005 4/27/2005
>Symbol Wk EPS Wk EPS Wk EPS Wk EPS
>UIS 1 4 88 90
>MAT 2 41 41 95
This is a good spreadsheet, but is not properly structured for a
relational table. In a relational database, "Fields are expensive,
records are cheap"; you should certainly NOT store data (dates) in
field names! A tall-thin table is the ticket (ticker?) here:
Symbol TradeDate EPS
UIS 4/22/05 1
UIS 4/25/05 4
UIS 4/26/05 88
UIS 4/27/05 90
MAT 4/22/05 2
MAT 4/25/05 41
MAT 4/26/05 41
<etc>
Symbol and TradeDate could be a joint two-field Primary Key since they
uniquely identify the record.
John W. Vinson[MVP]
.
- References:
- Prev by Date: Table Design
- Next by Date: Re: how do i setup a field in office access to automatically assign 4.
- Previous by thread: Re: Don't hate the rookie....please help -- simple question
- Index(es):
Relevant Pages
|
