AnsweredAssumed Answered

Database design theory and subsequent querying

Question asked by JeffreyG on Jan 2, 2009
Latest reply on Jan 4, 2009 by Jens Teich

Title

Database design theory and subsequent querying

Post

First of all, I will confess that I am the farthest thing from a database expert.  Having said that I am a convert from Windows and MS Access learning Filemaker.  I have always thought that database performance was optimized with long, skinny tables as opposed to wide ones.  For example, if a detail table was tracking sales by product, my assumption was that it would be better to have a table that looked something like this:

 

SalesEEID

Product

Month

Year 

SalesRevenue

 

over a table that  looked like this: 

SalesEEID

Month

Year

Product1SalesRevenue

Product2SalesRevenue 

Product3SalesRevenue

ProductnSalesRevenue 

 

QUESTION #1: Does that logic hold true with Filemaker?

 

Moving beyond the design theory, the next question is how to compare results for one period vis a vis the previous period?

The layout would have the month column and a base year column, a base year - 1 column and a calculated % chg field.

 

Any help is greatly appreciated!

 

Jeff

 

 

 

Outcomes