Form Design
in [Tables]
|
Prev: Compact & Repair Bug
Next: unique record numbers
From: TheDon on 4 Mar 2010 17:45 I feel fairly confident that I have my tables and relationships decently set. My problem now is how to display it for my staff to work with. I need some help with form layout Here's my scoop. I am re-building a camp database that was laid out on one entire table!!! So many fields... So many empty fields too. Nonetheless, we are moving onward and here is what I have... I have a camp database that has the following tables now: tblcamperinfo demographic info that may change (primary table) tblparentinfo info on parents and addresses could be more than one tblcmprcntyr describes info for current camp year. cabin, session, etc... changes every year. Will be purged or archived...(one to one) tblcmpracct financial information: tuition, payments, etc (one to one?) There may be a store account ledger added to one of the fields as a sub. tblcmprprofile a yearly profile and evaluation from the season (one to many) The above 5 tables all have a relating FK from tblcamperinfo PK where tblcamperinfo has a one to many relationship except tblcmprcntyr where it is one to one Most of my data entry folks want to be able to pull up and search mostly by camper name, but other factors too (like city, years attended) and also want to have mostly one place to add or change data and create new records. All registration comes in on one application. Returners have their record updated... I understand subforms, tabs, and all that, but I think I am missing the query part to put this all together. What is the best means for pulling all of this together on a form? Do I subform everything or create multiple forms? That may be too general, but let's start there. I really appreciate the help. thanks, Don
From: Al Campagna on 4 Mar 2010 19:04 TheDon, That's a pretty "broad" question for an answer with any real detail... Use the Tab Control to organize both your One to One data objects, and your One to Many data objects (subforms). You can get lot of data on one form that way. You can also just show the basic info for some of your subforms, with the ablity to "jump" (open a supporting form w/more detail) from a subform record, to the "full featured" form. Upon closing that, you return to the calling form. Perhaps... as you develop your main form... we can offer more specific answers to specific questions of design. Try starting (just a suggestion) with the camper info on the main form. Child's name, address, age, birthdate, etc.. etc.. And then the Parent information on a Parent page of a Tab control. Names, address, phone, work phone, etc -- hth Al Campagna Microsoft Access MVP 2007-2009 http://home.comcast.net/~cccsolutions/index.html "Find a job that you love... and you'll never work a day in your life." "TheDon" <TheDon(a)discussions.microsoft.com> wrote in message news:4FF55A84-D6F0-430D-A353-9A0D0765C926(a)microsoft.com... >I feel fairly confident that I have my tables and relationships decently >set. > My problem now is how to display it for my staff to work with. I need > some > help with form layout Here's my scoop. I am re-building a camp database > that > was laid out on one entire table!!! So many fields... So many empty > fields > too. Nonetheless, we are moving onward and here is what I have... > > I have a camp database that has the following tables now: > tblcamperinfo demographic info that may change (primary table) > tblparentinfo info on parents and addresses could be more than one > tblcmprcntyr describes info for current camp year. cabin, session, etc... > changes every year. Will be purged or archived...(one to one) > > tblcmpracct financial information: tuition, payments, etc (one to > one?) > There may be a store account ledger added to one of the fields as a sub. > > tblcmprprofile a yearly profile and evaluation from the season (one to > many) > > The above 5 tables all have a relating FK from tblcamperinfo PK where > tblcamperinfo has a one to many relationship except tblcmprcntyr where it > is > one to one > > > Most of my data entry folks want to be able to pull up and search mostly > by > camper name, but other factors too (like city, years attended) and also > want > to have mostly one place to add or change data and create new records. > All > registration comes in on one application. Returners have their record > updated... > > I understand subforms, tabs, and all that, but I think I am missing the > query part to put this all together. What is the best means for pulling > all > of this together on a form? > > Do I subform everything or create multiple forms? > That may be too general, but let's start there. I really appreciate the > help. > > thanks, > > Don
From: TheDon on 8 Mar 2010 12:45 Al, I went with your suggestion and it seems to be going alright. First stumbling block... I have to figure out a way to reperesent/enter camper activities. It seems to be a many to many... I have many campers who will be singing up for many activities. How do I get that to com up on the sub form correctly... Here is my relationship tbl Activities (15 activities all occuring 5 different times during the day) ClassID acttime actarea linking tble Camper ID PK Class ID PK tblcamperinfo Camper ID I laid out the form with tblcamperinfo as the primary set with a number of sub forms. I need to create this "Acivity" subform. Ultimately, we would want to print reports by Activity Area with lists of those signed up, then a report by "cabin" (from tblcmapercurrentyear) that would list each campers schedule... thanks a ton... Don "Al Campagna" wrote: > TheDon, > That's a pretty "broad" question for an answer with any real detail... > Use the Tab Control to organize both your One to One data objects, and > your One to Many data objects (subforms). > You can get lot of data on one form that way. > > You can also just show the basic info for some of your subforms, with > the ablity to "jump" (open a supporting form w/more detail) from a subform > record, to the "full featured" form. Upon closing that, you return to the > calling form. > Perhaps... as you develop your main form... we can offer more specific > answers to specific questions of design. > > Try starting (just a suggestion) with the camper info on the main form. > Child's name, address, age, birthdate, etc.. etc.. > And then the Parent information on a Parent page of a Tab control. > Names, address, phone, work phone, etc > -- > hth > Al Campagna > Microsoft Access MVP 2007-2009 > http://home.comcast.net/~cccsolutions/index.html > > "Find a job that you love... and you'll never work a day in your life." > > "TheDon" <TheDon(a)discussions.microsoft.com> wrote in message > news:4FF55A84-D6F0-430D-A353-9A0D0765C926(a)microsoft.com... > >I feel fairly confident that I have my tables and relationships decently > >set. > > My problem now is how to display it for my staff to work with. I need > > some > > help with form layout Here's my scoop. I am re-building a camp database > > that > > was laid out on one entire table!!! So many fields... So many empty > > fields > > too. Nonetheless, we are moving onward and here is what I have... > > > > I have a camp database that has the following tables now: > > tblcamperinfo demographic info that may change (primary table) > > tblparentinfo info on parents and addresses could be more than one > > tblcmprcntyr describes info for current camp year. cabin, session, etc... > > changes every year. Will be purged or archived...(one to one) > > > > tblcmpracct financial information: tuition, payments, etc (one to > > one?) > > There may be a store account ledger added to one of the fields as a sub. > > > > tblcmprprofile a yearly profile and evaluation from the season (one to > > many) > > > > The above 5 tables all have a relating FK from tblcamperinfo PK where > > tblcamperinfo has a one to many relationship except tblcmprcntyr where it > > is > > one to one > > > > > > Most of my data entry folks want to be able to pull up and search mostly > > by > > camper name, but other factors too (like city, years attended) and also > > want > > to have mostly one place to add or change data and create new records. > > All > > registration comes in on one application. Returners have their record > > updated... > > > > I understand subforms, tabs, and all that, but I think I am missing the > > query part to put this all together. What is the best means for pulling > > all > > of this together on a form? > > > > Do I subform everything or create multiple forms? > > That may be too general, but let's start there. I really appreciate the > > help. > > > > thanks, > > > > Don > > > . >
From: Steve on 8 Mar 2010 13:25 Don, Before you spend time developing a form and then find you need to redo it or even scrap it, you need a lot more work on designing your tables. The tables you posted here are not correct. Start with your camper table and post all the fields from your Excel workbook that pertain to a camper. Next, work on your activity table and post all the fields from your Excel workbook that pertain to an activity. Then we will work on joining the two. Alternatively, I could design all your tables for you for a small fee. Steve santus(a)penn.com "TheDon" <TheDon(a)discussions.microsoft.com> wrote in message news:55ACF42C-253C-407A-BB98-B7A8B367D518(a)microsoft.com... > Al, > > I went with your suggestion and it seems to be going alright. First > stumbling block... > > I have to figure out a way to reperesent/enter camper activities. It > seems > to be a many to many... I have many campers who will be singing up for > many > activities. How do I get that to com up on the sub form correctly... > Here > is my relationship > > tbl Activities (15 activities all occuring 5 different times during the > day) > ClassID > acttime > actarea > > linking tble > Camper ID PK > Class ID PK > > tblcamperinfo > Camper ID > > I laid out the form with tblcamperinfo as the primary set with a number of > sub forms. I need to create this "Acivity" subform. Ultimately, we would > want to print reports by Activity Area with lists of those signed up, then > a > report by "cabin" (from tblcmapercurrentyear) that would list each campers > schedule... > > thanks a ton... > > Don > > "Al Campagna" wrote: > >> TheDon, >> That's a pretty "broad" question for an answer with any real >> detail... >> Use the Tab Control to organize both your One to One data objects, >> and >> your One to Many data objects (subforms). >> You can get lot of data on one form that way. >> >> You can also just show the basic info for some of your subforms, with >> the ablity to "jump" (open a supporting form w/more detail) from a >> subform >> record, to the "full featured" form. Upon closing that, you return to >> the >> calling form. >> Perhaps... as you develop your main form... we can offer more >> specific >> answers to specific questions of design. >> >> Try starting (just a suggestion) with the camper info on the main >> form. >> Child's name, address, age, birthdate, etc.. etc.. >> And then the Parent information on a Parent page of a Tab control. >> Names, address, phone, work phone, etc >> -- >> hth >> Al Campagna >> Microsoft Access MVP 2007-2009 >> http://home.comcast.net/~cccsolutions/index.html >> >> "Find a job that you love... and you'll never work a day in your >> life." >> >> "TheDon" <TheDon(a)discussions.microsoft.com> wrote in message >> news:4FF55A84-D6F0-430D-A353-9A0D0765C926(a)microsoft.com... >> >I feel fairly confident that I have my tables and relationships decently >> >set. >> > My problem now is how to display it for my staff to work with. I need >> > some >> > help with form layout Here's my scoop. I am re-building a camp >> > database >> > that >> > was laid out on one entire table!!! So many fields... So many empty >> > fields >> > too. Nonetheless, we are moving onward and here is what I have... >> > >> > I have a camp database that has the following tables now: >> > tblcamperinfo demographic info that may change (primary table) >> > tblparentinfo info on parents and addresses could be more than one >> > tblcmprcntyr describes info for current camp year. cabin, session, >> > etc... >> > changes every year. Will be purged or archived...(one to one) >> > >> > tblcmpracct financial information: tuition, payments, etc (one to >> > one?) >> > There may be a store account ledger added to one of the fields as a >> > sub. >> > >> > tblcmprprofile a yearly profile and evaluation from the season (one >> > to >> > many) >> > >> > The above 5 tables all have a relating FK from tblcamperinfo PK where >> > tblcamperinfo has a one to many relationship except tblcmprcntyr where >> > it >> > is >> > one to one >> > >> > >> > Most of my data entry folks want to be able to pull up and search >> > mostly >> > by >> > camper name, but other factors too (like city, years attended) and also >> > want >> > to have mostly one place to add or change data and create new records. >> > All >> > registration comes in on one application. Returners have their record >> > updated... >> > >> > I understand subforms, tabs, and all that, but I think I am missing the >> > query part to put this all together. What is the best means for >> > pulling >> > all >> > of this together on a form? >> > >> > Do I subform everything or create multiple forms? >> > That may be too general, but let's start there. I really appreciate >> > the >> > help. >> > >> > thanks, >> > >> > Don >> >> >> . >>
From: John... Visio MVP on 8 Mar 2010 13:33
"Steve" <notmyemail(a)address.com> wrote in message news:e4dTEzuvKHA.732(a)TK2MSFTNGP06.phx.gbl... > Don, > > Before you spend time developing a form and then find you need to redo it > or even scrap it, you need a lot more work on designing your tables. The > tables you posted here are not correct. Start with your camper table and > post all the fields from your Excel workbook that pertain to a camper. > Next, work on your activity table and post all the fields from your Excel > workbook that pertain to an activity. Then we will work on joining the > two. Alternatively, I could design all your tables for you for a small > fee. > > Steve Don, before doing business with anyone, check out their credentials. You have to seriously question the ethic of anyone who knowing preys on new users in newsgroups that are set up for FREE peer to peer support. The fact that he constantly has to use this tactic says a lot about the fact that he can not compete in a fair market and that he has little repeat business. Stevie is our own personal pet troll who is the only one who does not understand the concept of FREE peer to peer support! He offers questionable results at unreasonable prices. These newsgroups are provided by Microsoft for FREE peer to peer support. There are many highly qualified individuals who gladly help for free. Stevie is not one of them, but he is the only one who just does not get the idea of "FREE" support. He offers questionable results at unreasonable prices. If he was any good, the "thousands" of people he claims to have helped would be flooding him with work, but there appears to be a continuous drought and he needs to constantly grovel for work. Please do not feed the trolls. John... Visio MVP |