[AccessD] Question of Approach

>>> Gary Kjos <garykjos at gmail.com> 1/28/2014 3:20 PM >>>
I'm assuming there can only be one of each age survey for each client? I would have a form for each survey I think.
 
***** No, I don't think so Gary. I'm not 100% positive, and I am currently waiting for an answer from this "client" regarding this. From our earlier conversations though, it seems that they can take a survey every year (I'm just throwing that time frame out there). This does make sense if you look at the ages for the surveys...the 2nd level survey is for kids 4-18. 
 
One of the options I had been contemplating is to combine the surveys and just enable/disable fields based on age. Some of the questions are the same, while others are more age relevant...for example the 1st survey (6 mo to 4 yrs) has questions regarding pacifiers and bottles.  There are only 42 questions among the 3 (17, 12, 13), and several questions overlap...I just realized this morning, that surveys 2 & 3 only differ by maybe 2 questions. 
 
 
I would tend to think of subforms where you have multiple "child" records for a parent record so you can maintain those multiple child to parent connections. I would have a client entry form to enter/maintain the client info and then link to the survey form which would perhaps be a pop up form for each survey age group. 
 
***** That is why I pointed her this way...multiple surveys for each client child.  But, something wasn't done right from the get-go, and w/the multiple surveys types...I've also started going back to scratch. I'm thinking, if I do it myself, from the top, then maybe I'll just do it correctly. 
 
But truth be told I'm way out of touch with actual ap development now a days. I just use Access as a query tool against Oracle databases with
output going to Excel.
***** Yeah, my involvement w/Access WAS decreasing as well. But, it seems to be feast or famine for me here...I won't touch it much, if at all, for a year or so, and then I'll get a bunch of work regarding Access. Right now I'm going through a heavy Access period...it started at the beginning of the month, when I was called down to the Treasurers Dept because their "College Chargeback" program wasn't working. I spent a week on that, and as that began I was contacted by our Sheriff's dept to write a program for them...I haven't actually WRITTEN a program for a while, so I jumped at that one. Now, this issue popped up the end of last week, causing me to take a break from the Sheriff's program. 
 
Just before all this began, I was actually called down to the Real Property Dept, because their Tax Program wasn't working. This was Visual FoxPro, which made me cringe...I loved DOS FoxPro (2.6), but I fell away from it with Visual...just don't care for it. Anyhow, this wasn't so much a program issue, as it was a user issue...the person doing that job had recently retired. The new person really doesn't know what she should, to be doing the job. She was getting by, by just going to recent programs and projects run. When she could no longer use the previous user's Window's Profile that data was no longer available. I copied the profile data over to a new directory and it worked...they thought I was a genius...I was a little disguted, to be honest, that THIS person was going into a position they just are not qualified for. Oh well...that is government...

I do know that you have to be comfortable with the design of what you are working on or you will be battling it over and over. So if you don't like
it as a subform, make it to standalone forms. 

How is the database relationships. that is usually where newbe or user developed systems are weakest. You need to nail down the database structure
correctly before you worry about the forms don't you?
 
***** To be honest, I just don't spend the time on relationships that I used to...and so far, I haven't suffered any ill effects, while I've saved a bunch of time. 

Notice: This electronic transmission is intended for the sole use of the individual or entity to which it is addressed and may contain confidential, privileged or otherwise legally protected information. If you are not the intended recipient, or if you believe you are not the intended recipient, you are hereby notified that any use, disclosure, copying, distribution, or the taking of any action in reliance on the contents of this information, is strictly prohibited. Niagara County is not responsible for the content of any external hyperlink referenced in this email or any email. 
IF YOU HAVE RECEIVED THIS TRANSMISSION IN ERROR, PLEASE NOTIFY THE SENDER IMMEDIATELY BY EMAIL AND DELETE THE ORIGINAL MESSAGE ALONG WITH ANY PAPER OR ELECTRONIC COPIES. 
Thank you for your cooperation.