Jump to content

Another Dynamic Value List Puzzle


Mindi

This topic is 6999 days old. Please don't post here. Open a new topic instead.

Recommended Posts

I need a dynamic value list but have not seen any examples of exactly what I need.

I have 2 tables... LEADERS & GROUPS

Each GROUP needs to be assigned a LEADER.

I get the LEADER value list from the LEADER table... not a problem.

But once a LEADER has been assigned to a GROUP I no longer want them to display on the value list.

I have tried various things... but nothing seems to quite work and I am at my wits end!

Link to comment
Share on other sites

Mindi:

Not sure I understand exactly. Do you mean that the two value lists both draw from the same table? Do you also mean that essentially you want to draw two leaders from the Leader table, but they have to be unique?

-Stanley

Link to comment
Share on other sites

Ok... So I thought this would be the answer.... After tearing up my database to trying & make this work I realized that in the sample database that the same staff members could be assigned to different projects. They just could not have the same staff member on one project... I need to totally remove a person from the value list once they have been assigned... Any thoughts?

Link to comment
Share on other sites

I believe that as long as a Leader can hold only one appointment, you can keep adding Leaders to a Group.

All you need to do is add a new Leader_n_ID field, add this field to the cLeadersIDs concatenation calc, duplicate a script and modify it to pop the new field.

Whether this is the optimal solution for the problem is a separate question. It is difficult to advise when you keep changing the rules.

Link to comment
Share on other sites

I guess I just never fully explained it. But each of your solutions have been great... and going step by step has made me understand what you are doing. So it really has been very helpful to me even if it has been time-consuming and frustrating for you. So thank you very much for your help!

You can have a maximum of two leaders per group and a leader can only have one assignment. Your last database example would actually work but having 2 LeaderID fields prove to be problematic later in reporting. Which is why I thought that a link table would be the solution...

Link to comment
Share on other sites

A link table is only necessary in a many-to-many type of situation. If a leader could lead more than one group, AND a group could have more than one leader, then you would need a link table.

If I knew we were to going to end up with multiple leaders per group, I'd say wait a minute - you call them leaders, but if I decide to call them members, then it's pretty clear what needs to be done: instead of assigning a leader to a group, we should be assigning a group to a leader. And suddenly everything is much easier, as you can see.

LeadersGroups.fp7.zip

Link to comment
Share on other sites

One more thing... the solution that -Queue- offered from NightWing used a link table and you could use a portal to display information. It worked except that you could re-use staff members on different projects... which was why I liked your solution better... yours was simpler & more direct.

Link to comment
Share on other sites

This topic is 6999 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.