Relationship Help
in [Tables]
|
From: lettyg on 23 Dec 2009 12:02 I have uploaded a screen shot of my relationships window for the database I have designed. I believe what i want is a one to many relationship. The Parent Table is FCCaseInfo and its primary key is CaseIdNo. The child tables should be FVVW, FVCharges, and FVDates these tables also have the CaseIdNo (not primary, but i added this field to somehow relate all of these together). Any suggestions as to what my relationships should be? Thanks!
From: lettyg on 23 Dec 2009 12:04 I have uploaded a screen shot of my relationships window for the database I have designed. I believe what i want is a one to many relationship. The Parent Table is FCCaseInfo and its primary key is CaseIdNo. The child tables should be FVVW, FVCharges, and FVDates these tables also have the CaseIdNo (not primary, but i added this field to somehow relate all of these together). Any suggestions as to what my relationships should be? Thanks! http://cid-af7c698d9d142706.skydrive.live.com/self.aspx/.Public/Database.JPG
From: Jeff Boyce on 23 Dec 2009 12:42 You know your topic much better than we do ... You need to tell US what the relationships are! For example, how many [FVVW] records could you see for each single CaseIDNo (parent record)? How many [FVCharges] records per CaseIDNo? ?[FVDates] per CaseIDNo? (by the way, we're taking you at your word that [FVVW], [FVCharges], and [FVDates] are "child" tables. But you haven't described the type of data that you're storing in any of the four tables, so we're unlikely to be able to offer our observations on whether you have modeled your data relationally, or have "committed spreadsheet".) More info, please... 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. "lettyg" <lettyg(a)discussions.microsoft.com> wrote in message news:EF01C3E8-FE3A-43CC-8F79-A299D9F06E16(a)microsoft.com... > > > I have uploaded a screen shot of my relationships window for the database > I > have designed. I believe what i want is a one to many relationship. The > Parent Table is FCCaseInfo and its primary key is CaseIdNo. The child > tables > should be FVVW, FVCharges, and FVDates these tables also have the CaseIdNo > (not primary, but i added this field to somehow relate all of these > together). > > Any suggestions as to what my relationships should be? > > Thanks!
From: Fred on 23 Dec 2009 13:32 IMHO, if you put the CaseID number into those three "child tables" are are able to put a single CaseID number into that field in each of those child records, the you have already essentially created and told us about the relationships, determined that they are not many-to-many, and all that remains is to "draw the lines" between the CaseID field to the field of that name in each of the child tables. You'll still have some secondary choices to make (referential integrity and which, if any, unmatched records that you so (which will presumably be those of your parent table)
|
Pages: 1 Prev: design help needed Next: Access Many to Many relationship |