Portal Pull-Down Menu only Working Record 1?

[MMBadger]

I have a portal on a layout that uses a pulldown menu to populate the first field of the record. Once one record is in, though, it won't allow me to use the pull down menu again...I have specified that the relationship can be used to create records, so it isn't that. Is this just a wierd FM7 quirk or am I doing something wrong?

[MMBadger]

I've done some further investigation, and the value list will open when you allow it to show all records, but when you ask the value list to show only related records, it won't open past the first portal row (this is when the value list is based on values in a field). Hoping someone can help me solve this!

MMB

[-Queue-]

Is it a self-relationship that determines which values should display? If so, this sounds similar to the gripe that's prevented me from being too serious about FM7.

[MMBadger]

Nope. In the main file (Programs) I enter a value into a Lodging Property field. This value is connected by a relationship where Lodging Property Name = Company Name in a second file (Vendors). I then take a relationship between Vendors and Vendor Contacts (another table in the Vendors file) to pull up contact names for the chosen property. These are entered into a portal (referencing a 2nd table in the Programs file) that tracks which contacts at the chosen Lodging Property are specific to the Program at hand (i.e. of 10 possible contacts, just 2 or 3 are typically knowledgeable about a given Program). The value list I'm using asks to pull only related values from the Vendors/Vendor Contacts relationship so that I only see Contacts for the specific property I've chosen, and not all contacts within the Vendor Contacts table. When I ask for only related, it won't pull up the value list after the first portal entry. When I ask for all, it "works", but is confusing because it pulls up every possible Vendor Contact from every possible Vendor!

Hope that makes sense. It's tremendously frustrating, and I keep running into it without a fix!

I'm beginning to think this is a FM7 bug...hopefully someone can prove me wrong!