I am very new to database creation so I appologize if my newbieness gets in the way.

I am creating a database for my own record keeping purposes as a Montessori teacher. I want to have a few sets of checklists on a table of the presentation I am about to give. The first would have the names of students who have not been given the presentation at all, the second and third are a list of those that have had it and may receive it again. Like this:

If class is- Bobby, Suzie, Janie, Richy, Harry

List 1- Suzie, Harry

List 2- Bobby, Richie, Harry

List 3- Bobby, Richie, Harry

I have value lists for List 2 and List 3 which comes from a table of the presentations given and a value list for the entire class that comes from the student records- not easily related. I cannot figure a way to make a value list that is class - list 2. Is there some way to do this given the information I have provided?

I can provide the greater context if there is not enough information here though what I have created makes my eyes go cross.

I have already worked through the teadium of separating the checkbox results to make them usable (thanks to other people's questions), so that is not a problem.

Thanks for your help!

-James

If you have one list could the ValuelistItems( and the "not equal" relationship, make a new dynamic valuelist where the stuff from the first VL is omitted. But I can't quite see if you've taken the plunge into relations yet??? I made a template some time a go, I called "Monkeyclass Dwindle" that might be a lead for your??

http://www.fmforums.com/threads/download.php?Number=133792

...which must be the best, when custom functions is out'a reach - not that they're faster, but they're easier to implement!

http://www.briandunning.com/filemaker-custom-functions/detail.php?fn_id=142

...but you have to own a 7Dev licence to use it!!

--sd

Thanks S

RecordExample.fp7.zip

jib,

I have just had to produce the same results and have come up with the attached solution. It may be a bit elementary for some of the guys here though. Each new record in table 1 will have all other values in table 1 excluded without using scripts. You can build the relationships on calculation fields to suit your needs.

Value1.zip

Thank you Onefish. When I have the time I will look at your attachment to see if I can get something there to work for me. I am afraid however that the relationships I need to maintain are more complex...

-Jib

Each new record in table 1 will have all other values in table 1 excluded without using scripts.

You have the same syncing-problems, I struggled with!!! You have to stress the importance of the word "NEW" record, because if you try to alter a previous entry isn't the dwindling correct any more!

--sd

Yip,

I noticed that but it is not a big deal in my current application as the value list is only required at creation of new records via a custom dialog box which allows the user to abort creation of the record if the desired value is not in the list. After that the user will not have access to the field again (except viewing). jib, from what table do you need to use the value list? This is important as the value list will have to show only related values starting from?:

It has to start from Presenting.

Thanks for explaining, I will take a closer look at the file you sent this weekend. I hadn't though of custom dialog boxes...

Best,

-Jib

jib,

Before you go too far with the custom dialog box, you cannot create them to have a field formatted as a pop up list without a plugin. I'll have a look at your test file tomorrow.

I've got something that seems to work, according to how I've interpreted the logic anyway. It is pretty tricky. It is an extension of the technique that onefish used.

First of all I think that some of your data is not in the right place. IMHO, you should not use such things as checkboxes in the Presenting table to hold the data of student attendance at presentations; that data is already in, and belongs to the Individual Records table. Checkboxes, by their very nature, are suspect, in that they store multi-line data; useful for secondary info, but not a good way to handle basic structural data. Student attendance is the most critical data in your structure. Portals are a better structure.

Also, if there are multiple instances of the "same" Presentation Name, in Presenting, then Presentation in that table is simply another instance, on another date/time. So, an attribute of "re-presentation" for student means that they would be available for the "next" presentation of that Presentation Name. Anyway, that's my interpretation. I first did it with just the Presentation as you wrote it, so it could be switched back to that.

I also concluded that if a student was marked as available for re-presentation, then attended a 2nd presentation, his previous re-presentation mark should be cleared, so he no longer appears in the available list unless re-marked. This becomes important if there is a 3rd presentation. So a self-relationship and Loop was added to do that.

PresentationsStudents.zip