pop up list

[tfman716]

Ok i have a pop up list that has three choices...November, February, and June. I have a main form which contains a whole bunch of radio buttons. I want to be able to choose a month, say November, and have the form show up with all the appropriate buttons, yes or no, clicked. So what I basically want to happen is for all the data for November to show up when November is clicked. Then when February is selected I want all the data from November to appear and allow the user to change some answers from yes to no. So when November is selected again...Only the data that was selected for November appears...and so on...This is a report card sort of thing so it tracks the progress of students so when they complete a task the teacher selects yes and if they havent completed a task they select no. Hopefully by the time June comes around all the buttons say yes...But I want them to be able to see what they did in November and what improvements they made...Is there any way to link the pop up list to the form?? and store the data seperately for each month??? Thanks for the time

[Fitch]

1. I think you'll need a button to click after you select from the popup; therefore, I'd suggest not using a popup at all, but just using three buttons instead.

2. I should think you'd have your student info in one file, and your progress info in another, related file.

3. The student file has the buttons, and a global text field, let's call it gStudentProgress.

3. The progress file has a calculated text field, let's call it cStudentProgress, the calc is:

StudentID & "-" & theMonth

4. There is a relationship gStudentProgress::cStudentProgress

5. Clicking one of the buttons sets gStudentProgress to StudentID & "-" & "November" for example.

6. The button might check to see if IsEmpty(progress::someField) -- meaning that month doesn't exist yet for that student -- and if so, ask if you want to create it.

7. Now that I think about it, it may be instead of all that, you want to start off simple -- just have a relationship by student id, and a button to click that goes to the related progress records for that student. In the related (progress) file, have a button that lets you create a new record, and that would duplicate the existing month etc. Another option would be to show the related progress reports in a portal in the student file. You could then click a button in the portal to go to the desired month.

Hope that gave you some ideas.

[tfman716]

Ok now for number 7...just have a relationship by student id, and a button to click that goes to the related progress records for that student. In the related (progress) file, have a button that lets you create a new record, and that would duplicate the existing month etc.

What do u mean by that?? When you say (progress) file do u mean another new database? Also, the records that I think you are referring to are all stored in seperate radio buttons. There is like 50 criteria that a student has and each one is a seperate radio button...Yes or No...I will try and play around with your ideas...Thanks a lot

[tfman716]

Ok this kind of works

I created both buttons and the relationships as stated in 7. When I click the button that goes to the related file it brings up every student that I have on file and I only want it to bring up the student whose record I am viewing. Then when I click the Add records button I will be adding records for only that student...How do I get the relationship from the record I am viewing??

[Fitch]

Yes, Students should be in one file, and the three progress reports in another file (e.g., Progress).

Each record in your Student file should have a unique ID. This is generally referred to as the "primary key" field. Each record in the Progress file also needs a field to store the ID from the Student file (this is called the foreign key).

[Fitch]

Oh, and make sure the GTRR (Go to related) script also has the checkbox checked for "show only related."