Ed
You could create a table called Seats. Then, once you have entered the
number of Tables and the number of Seats in a table of Preferences, you
can have a script create a series of Tables*Seats records, one for each
seat at each table, and each containing the table's ID and the seat's ID.
The names can be entered from a drop down list as desired.
To have a drop down list of names, you create a table of Names, and a
value list, AllNames, of all the names in the table.
To restrict this value list to those names not already placed:
- create in Names, a text field, Placed,
- create in Seats, a global text field, gNo, containing "No",
- create a table occurrence, seats_NAMES_NotPlaced, relating the
fields gNo in Seats and Placed in Names,
- create a value list, NamesNotPlaced, using values from Name in the
table occurrence, seats_NAMES_NotPlaced, and including only related
values starting from Seats.
- format the field Name in the list layout of Seats to display as a
drop-down list values from NamesNotPlaced.
- also format this field to trigger, OnObjectModify, a script which
sets the field, Names::Placed for the name selected to "Yes".
Let me know if you would like to see the scripts or my demo file.
Ross
Ed Bullock wrote:
> Hi Agnes,
>
> Thank you for your reply. I was not able to locate this demo file but while
> searching for it I did find reference to a demo file by Excelisys of a drag
> and drop technique which is very impressive and I can probably use in my
> solution. I have downloaded this demo and it works very well.
>
> I can envisage how this will work by dragging names and dropping them onto a
> table but I do have 1 issue.
>
> This technique uses a mix of portals, relationships, script triggers and
> container fields.
>
> If I knew how many tables there were and how many seats at each table then
> this would be fairly straight forward... but I don't.
>
> The user should be able to select how many tables are in a room and how many
> seats at each table.
>
> I can obviously not setup the correct number of portals, relationships,
> container fields etc before I know how many portals will be needed (1 per
> table)
>
> In effect I need this part of the database to build itself once the user has
> selected the options but I cannot see this being possible.
>
> Does anyone have any bright ideas?
>
> Many thanks
> Ed
--
This list is a free service of LassoSoft:
http://www.LassoSoft.com/Search the list archives:
http://www.ListSearch.com/FileMaker/Browse/Manage your subscription:
http://www.ListSearch.com/FileMaker/
