 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Database Design / January 2005HELP! I can't keep track family address, phones, dates, etc.
I want to creat an Access Data base that would start with my parent(s) page with their page having a drop down list of their children (me and 6 others) linking to an individual child page of our info, further linking to pages for our spouse, children and so on for a couple of generations. Each individuals pages would have fields for name, spouse, addresses (home, company name/work, vacation home) phone numbers (home, work, fax, cell, other) Date of birth (with current age calculation automatically inserted) Date of Death, date of marriage, e-mail addresses, etc. Reports would be an address book, alphabetical lookup by first or last names, selected mailing labels, etc. It would be neat to have the cover page have areas (button) for Mom/Dad photo, each child, by clicking the photo you go to that persons main info page with spouse and child links from drop down lists..... To store the data have one table, tblPerson, for every one uidPerson Name Forename DOBirth DODeath Photo fkPerson_Father fkPerson_Mother fkPerson_Spouse fkPerson_Father and fkPerson_Mother fkPerson_Spouse relate back to uidPerson (in a self-join / pigs-ear relationship). This is only a start HTH, Graeme. Hello, Thank you for your response but being new to Access I really do not understand what you mean or what the list of items you listed means. uidperson, fkperson, etc. Could you further expound on this? I don't have a clue where to start from your information. THANKS! Ted Pagels FIREPROSe, LLC > To store the data have one table, tblPerson, for every one > [quoted text clipped - 13 lines] > This is only a start > HTH, Graeme. One Relational table can be used to store every (biological) ancestor for a person. uid is unique id / primary key (use AutoNumber data type) fk is foreign key (link to a primary key in a related table) (use Data Type: Number; Field Size: Long Integer) Create the one table, call it tblPerson. Open the relationships window (Tools > Relationships menu from the Database container window) and add the table 4 times (it'll appear as tblPerson, tblPerson_1, tblPerson_2, tblPerson_3) Drag a link from (and, for completeness enforce referential integrity): tblPerson_1.fkPerson_Father to tblPerson.uidPerson tblPerson_2.fkPerson_Mother to tblPerson.uidPerson tblPerson_3.fkPerson_Spouse to tblPerson.uidPerson so, looking at a person record, you can trace who the father is/was by taking the value from the fkPerson_Father field and searching the table for that primary key value. Try it, come back with questions. Graeme. Hello, I'm so sorry but I just don't understand what you are trying to tell me what to do where do I start, with a template or what? Again I'm new to Access. I do not know what to try. Do you have a template available to start from that you can e-mail to me or I can look up someplace easy? I don't know what a relational table is or the other abbreviated abbreviations such as foriegn key??? > One Relational table can be used to store every (biological) ancestor for a > person. [quoted text clipped - 20 lines] > Try it, come back with questions. > Graeme. Hello, I'm so sorry but I just don't understand what you are trying to tell me what to do where do I start, with a template or what? Again I'm new to Access. I do not know what to try. Do you have a template available to start from that you can e-mail to me or I can look up someplace easy? I don't know what a relational table is or the other abbreviated abbreviations such as foriegn key??? > One Relational table can be used to store every (biological) ancestor for a > person. [quoted text clipped - 20 lines] > Try it, come back with questions. > Graeme. MS Access has a relational database engine called jet. The terms I've supplied are common expressions used in Relational database design. Relational databases is a large subject. For an introduction try the help files. Microsoft have online tutorials also. This is just one link (I haven't studued the whole 'course') http://office.microsoft.com/training/training.aspx?AssetID=RC061181381033 I don't think there's a wizard to create the table. You could start by uisiong the wizard to create a contact table and modify it. Graeme. Thanks so much I'll try that! PEACE! > MS Access has a relational database engine called jet. > The terms I've supplied are common expressions used in Relational database [quoted text clipped - 9 lines] > > Graeme. > Hello, > [quoted text clipped - 4 lines] > relational table is or the other abbreviated abbreviations such as foriegn > key??? GraemeR is right. Relational Databases are a *huge* topic. I started out writing a quick primer on it, and two hours and four pages later (of trying to make it as simple as I could), I realized that nothing I could put in anything less than a chapter length work could even hope to scrath the surface (and I was doing my best to illustrate the difference between MS Access and most RDBMS software along the way . . .). Sincerely, Chris O. >I want to creat an Access Data base that would start with my parent(s) page >with their page having a drop down list of their children (me and 6 others) [quoted text clipped - 8 lines] >each child, by clicking the photo you go to that persons main info page with >spouse and child links from drop down lists..... I hope Graeme will forgive me for jumping in here. His advice is (as usual) right on the mark but I see you're having difficulty with the jargon. In Access, you need to design your database starting with the Tables. You need to identify the "Entities" - real-life people, things, or events - of importance to your application; each kind of Entity gets its own Table. You then need to figure out the relationships between the entities - which, in the case of geneology, can be surprisingly complicated (step-parents, just for example: not only can one person have several children, one child might - like me - have two mothers as well as a father). Don't jump into designing your data entry forms or your reports too soon! The first thing to do is to set up Tables to store the information you want. These constitute the foundation of your building; the forms and reports are the superstructure and come later. I'd start with a People table: People PersonID <Autonumber, a unique identifier for a given person> BirthLastName BirthFirstName CurrentLastName <married name, or for name changes> CurrentFirstName <some people change their name of course> Nickname DateOfBirth [Date/Time] <note that you can't use approximate dates> DateOfDeath Addresses AddressID <autonumber> Address1 Address2 City StateProvince PostCode <don't use Zip, you might have relatives in Canada or Zimbabwe> PeopleAddresses PersonID AddressID MailingAddress Yes/No <this lets multiple people have the same address, or lets one person have several addresses> RelationshipTypes RelationshipType Text <Spouse, Sibling, Child, Parent> Relationships PersonID1 PersonID2 RelationshipType RelationshipDate RelationshipEndDate Note that you should not put a MarriageDate in the People table; especially these days, a given person might have zero, one, two, or more marriagedates. Instead the date that a marriage relationship begins is a property OF THE RELATIONSHIP, not of either person. You'll have a fair bit of work setting up Forms and Subforms for this, but it's all doable. John W. Vinson[MVP] THANKS! Now I may start this project as time permits or find some high school kid that will probably get it done in an hour or two and I'll pay them!! > >I want to creat an Access Data base that would start with my parent(s) page > >with their page having a drop down list of their children (me and 6 others) [quoted text clipped - 74 lines] > but it's all doable. > John W. Vinson[MVP] >THANKS! Now I may start this project as time permits or find some high >school kid that will probably get it done in an hour or two and I'll pay >them!! <chuckle> "You can have it fast, cheap, or correct. Pick any two." I'm a professional database developer. I wouldn't touch an app like this with a bid under 20 hours, as you describe it. Geneology is TRICKY and full of unexpected traps. On the other hand, it's also popular. There are LOTS of good family-history programs on the market. Go to www.google.com and do a search; you may be able to find one that meets your needs already built. John W. Vinson[MVP] Thanks for the advice! I'll try a look up search. TJP > >THANKS! Now I may start this project as time permits or find some high > >school kid that will probably get it done in an hour or two and I'll pay [quoted text clipped - 12 lines] > > John W. Vinson[MVP] |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.