Multiple Joins in a Query Design
in [General]
|
Prev: non editable record
Next: Project Gallery-- Newsletter
From: FifthRing on 16 Mar 2010 21:23 Thank you! I finally figured out a plan of attack based on your suggestion to add 60 rows instead of 60 columns like I was thinking. That is completely new way of looking at things ! I love your quote: "Fields are expensive, records are cheap". Thanks again. "John W. Vinson" wrote: > On Tue, 16 Mar 2010 15:47:01 -0700, FifthRing > <FifthRing(a)discussions.microsoft.com> wrote: > > >The second table has dates I want to take a look at the stock prices. I > >have 60 dates that I want to look at out of the years worth of data and the > >dates are different for each stock. I just call them date1, date2, date3, > >etc. > > That's an incorrect design. What if you want *70* dates someday!? > > "Fields are expensive, records are cheap". Rather than one row with 60 dates, > consider using one datefield with 60 rows. Then a very simple join will get > your result. > -- > > John W. Vinson [MVP] > . >
From: John W. Vinson on 16 Mar 2010 23:07
On Tue, 16 Mar 2010 18:23:01 -0700, FifthRing <FifthRing(a)discussions.microsoft.com> wrote: >Thank you! I finally figured out a plan of attack based on your suggestion >to add 60 rows instead of 60 columns like I was thinking. > >That is completely new way of looking at things ! > >I love your quote: "Fields are expensive, records are cheap". > >Thanks again. You're welcome! Glad that I was able to help. Here are some deeper wells of insight: Jeff Conrad's resources page: http://www.accessmvp.com/JConrad/accessjunkie/resources.html The Access Web resources page: http://www.mvps.org/access/resources/index.html Roger Carlson's tutorials, samples and tips: http://www.rogersaccesslibrary.com/ A free tutorial written by Crystal: http://allenbrowne.com/casu-22.html A video how-to series by Crystal: http://www.YouTube.com/user/LearnAccessByCrystal MVP Allen Browne's tutorials: http://allenbrowne.com/links.html#Tutorials -- John W. Vinson [MVP] |