Hi, I am creating a database for a talent agency and am currently working on assigning ROLES to PROJECTS and then assigning TALENT to ROLES.

I have a layout for projects with a portal to the "roles" table for creating roles for the project.

I also have a layout for projects with a portal to the join table for roles and talent. So from the portal on the project page you can select a role related to the project and then select a talent to assign to that role.

The actual join table layout for role/talent (which ultimately will not appear on the database but which I use to test and make sure records are created properly through the portal) works great. On the join table layout I can choose a role and a talent by the ID key fields and then have the role name and talent name appear on that layout from a field from their source table.

However, I have a problem with the portal on the project page linking to the role/talent join table (all the fields in my portal are the same as the ones I used on the join table layout):

1) Without there being any records in the role/talent join table, the "role name" field in the portal auto enters the first role name created for that project. (It does not do this in this field on the actual join table layout.)

2) Then, in the portal when I DO select a talent and a related role (through ID keys) it does not change the role name that is displayed on the portal - it stays as the name of the first created role for that project. The talent name displays fine.

The join table record that was created through this portal, however, DOES display the proper role name and it does not auto enter anything when a new record is created there.

There is no auto enter specification for role name field (from the "roles" table) and it is not a global field so I can not figure out why it only displays one role name regardless of what role is selected through the portal...so I'm assuming this may be a relationship criteria issue?

Please let me know if more information would be helpful - such as field names and tables, etc.

Edited December 8, 200916 yr by Guest

Roles is related directly to Projects, and the field Roles::RoleName returns the value from the first related record in Roles, regardless of the portal.

You need to either:

• place another occurrence of Roles on the graph, and relate it to the join table by RoleID; then show the RoleName field from this occurrence in the portal;

or:

• define a calculation field in the join table =

Roles::RoleName

and use it to display the name in the portal.

BTW, the relationship between Roles and the join table can (and probably should) be based on RoleID alone. The ProjectID is known from the parent record in Roles.

Awesome this works perfectly, I knew I was missing some important piece of information. I did relate the join table by RoleID alone and defined a calculation field for the role name.

Thanks for your help!