design issue
- From: Darren <darrenburgess1967@xxxxxxxxx>
- Date: Fri, 26 Oct 2007 14:17:22 -0700
Hello,
I have a design issue that I am struggling with. (sorry for the long
post, and thank you for your patience)
Here is the context:
Multiuser, server-based FMP 9 solution for a large membership
association.
3 tables : Members, Meetings, and Registrations (a join table between
Members and Meetings)
On a meeting layout, a user can click on a Portal list of registered
members to see detail information for that member. In my current
solution, I simply have two side by side portals, one is a just a list
of names, the other is a one row portal with all of the detail. I use
Goto Portal Row to get to the correct detail, as they are sorted the
same.
This creates a few problems. One is that the user can scroll in the
detail portal and then it appears that the two portals are not synced
up. The other is that when I navigate between meeting records the
portals do not match up - the detail portal goes back to the first
portal row.
One solution would be to set a temp global key field to the
registrationkey for the particular registration that I want to see
detail on, and then display data based on the relationship between
this globalkey and the registration table. The problem here is that
when I navigate between meetings this globalkey will be the same for
all meeting records and as such will only work for the meeting that
globalkey was applied in last.
The next solution has the tempglobalkey not be set to global storage,
so that each meeting has its own value for the tempkey. The problem
there is that users looking at the same meeting will undo each others
preference as they are working.
So I think I need to link my User table to the Meeting table with an
intervening join table that will store the users current registration
detail that they were looking at.
Its just that when I start thinking about the scripting involved with
this, and the controls that have to start going into navigation, my
head starts to spin.
There must be a simpler solution!? Anybody want to take a shot at
this? Help!
Darren
.
- Follow-Ups:
- Re: design issue
- From: Grip
- Re: design issue
- Prev by Date: Re: Leopard compatibility?
- Next by Date: Macintosh Filemaker home inventory template
- Previous by thread: Multiple Date Input...
- Next by thread: Re: design issue
- Index(es):
Relevant Pages
|
|