A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Another relationship question



 
 
Thread Tools Display Modes
  #11  
Old April 1st, 2010, 07:34 PM posted to microsoft.public.access.tablesdbdesign
Jeff Boyce
external usenet poster
 
Posts: 8,621
Default Another relationship question

When I posted, your response was not visible.

By putting ArtShowName and ArtShowAddress in the same table (along with
other fields), I don't see how the OP could trace back to the "parent" that
puts on those art shows... That first table looks more like an "instance
of" table (i.e., a "child")...

Regards

Jeff

"Steve" wrote in message
...
Jeff,

Thanks for repeating the same thing I said in my response to Rob an hour
and a half ago! Do you have any comments on the tables I suggested to Rob?

Steve





"Jeff Boyce" wrote in message
...
Oho!

Given the logic you just tried, then why not use the same "application"
over and over ... it's the same "show", right?g

I suspect what you're facing is that you have, for example, The Humongous
Bank Commission, which puts on a show each year. However, (and this is a
very big BUT) the show last year IS NOT the same as this year's show.
You have two instances of a show with the same name (and I'm almost
willing to bet that the names are different -- e.g., 2009 HBC and 2010
HBC).

In a way, it might be similar to offering a class on Roman History at the
University. You could have a different venue for each class (i.e.,
classroom), a different sponsor (i.e., instructor), a different ...
Some folks would (legitimately) point out that you most definitely do NOT
have the same show each time, merely shows sponsored by the same
organization, or shows presented in different time frames, venues, etc.

I'm willing to bet that the records for [Applications] and [Results]
pertain, not the the parent, but to the specific child instances.

If this is a fair assessment, then you need a table to keep the parent
level organizations or show-names or ..., then a child table to hold each
of the instances of those. Then it is the primary key of those CHILD
instances that you need to have show up as foreign keys in your
[Application] and [Result] tables.

... and if you want to know your numbers related to a particular
organization/show-name, use a query and trace your way back through the
CHILD instance to its PARENT.

Good luck!

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"Rob H" wrote in message
...
I haven't started designing the forms, it's getting the relationships
setup
first that has me stumped.
Since you said one Show can have many Applications, and one Show can
have
many Results, do you have your tables related this way?

This is the answer that I think is key to my issue, would I use the
PK(Show
ID, auto number) in the Shows table and then link that to both the
Applications and Results table using a FK(number) in those tables? I've
tried so many different ways I'm not sure if I tried this one or not.

(I'm curious though, how a single Show could have more than one Results
record?)
This would be because I could attend the same show year after year and
would
want to see the results from each year listed individually.

Hope this helps.

"Jeff Boyce" wrote:

Rob

Help me a little bit more here ...

Since you said one Show can have many Applications, and one Show can
have
many Results, do you have your tables related this way?

Then, in terms of form design, are you using a main form to display the
[Show] record(s), and a subform for [Applications] and another subform
for
[Results]?

(I'm curious though, how a single Show could have more than one Results
record?)

Regards

Jeff Boyce
Microsoft Access MVP








  #12  
Old April 2nd, 2010, 01:23 PM posted to microsoft.public.access.tablesdbdesign
Fred
external usenet poster
 
Posts: 1,451
Default Another relationship question

I think that what Steve said is right and is fundamental to your solution.
And since he was only 5% as rude here is he usually is and didn't hit you up
for money as he often does to others, we should encourage that.

One of your underlying problems is/was that you are using the word "art
show" to refer to two fundamentally different entities. One is an entity
that transcends years, and the other is an "event" which is an instance of
that show running.


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 10:21 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.