I wonder if this can be done to avoid the use of validation calculations?

I want to find a VL filter that will prevent double bookings of room_names in the same time_slot; ie. once a room_name is chosen for with a time_slot in one record, that room_name no longer appears in the roomVL in other records.

Table1:rooms

comprises 8 "room_names"

Table2:Schedule

date

room

time_slot

time_slotsVL use "custom values", 8:00, 9:00, etc.

roomVL based on relationship, Table1::Table2, "use values from field" Table1:"room_names".

So, for example:

the user chooses the time_slot first (from time_slotVL) and then room_name from roomVL ....

record1, time_slot = 8:00, room3 (from VL comprising room1 through room8)

record2, time_slot = 9:00, room3 (from VL comprising room1 through room8)

and then, accordingly:

record1, time_slot = 8:00, room3 (from VL comprising room1 through room8 -- except room3)

what additional calc or relationship can accomplish this?

Edited May 26, 201015 yr by Guest

Bump -- so is there no way to eliminate an item in a VL if the value has been used in a found set?

I was looking for a "not =" self-join for the time_slot then use this as the "Include only related values" but I don't seem to get it.

Edited May 26, 201015 yr by Guest

Perhaps this topic has the answer for you. A dwindling value list?

http://fmforums.com/forum/showtopic.php?tid/185835/post/274656/#274656