Thank you for your post.
I am unable to replicate the issue with FileMaker Pro 13.0v1 running on Mac OS X 10.8.5 (and Mac OS X 10.9.1). Here are the steps I followed:
1. I created a new table "Names" with three text fields: First Name, Last Name, Phone Number
2. In the Relationships graph, I added a new table Occurrence for Names, "Names 2".
3. I linked the Phone Number field between Names and Names 2.
4. The Relationship allows creation of records in Names 2 as well as Delete related records.
5. I created a new record with the values "TSGal", "TSGal", and "1234" for First Name, Last Name, and Phone Number, respectively.
6. In the Layout, I created a portal into Names 2 and included all three fields.
7. I made the First Name field a drop-down list using values from Names.
8. In the Inspector for the Last Name field, I clicked the Data tab, and under Behavior, I set a calculation for "Hide object when" to:
Names 2::First Name = "TSGal"
9. In Browse mode, the portal only displays the First Name and Phone Number values (as expected).
10. I added a new record, entered "TSGal" for First Name, and the Last Name field becomes hidden and skips to already entered Phone Number.
11. I repeated step 10 more than 120 times. This never failed.
Please let me know what I'm doing differently than you so I can try to replicate the issue.
thank you very much for investigating TSGal,
i understand that cannot be replicated as i described it. my solution is very complex - the portal and the fields in the portal are loaded with triggers
- the portal and parent of portal are transactional - there are commits between row creation to keep the portal sorted when line items are inserted.
maybe i can create a simplified pruned file to you. the issue is really tricky because it works most of the time. maybe it is related to the delete portal row issue other users (incl. me) reported on a different thread.
I see a chance that this issue is caused by any calculation that didn't finish properly. I'ld recommend testing the script with tasks at the end:
- Commit Records [skip validation, Perform without dialog] AND/OR
- Refresh Window
I saw issues like this before which mostly got solved by a Commit Records step
thanx for your idea Benjamin, unfortunately i can't just commit whenever i like otherwise i am losing transactional integrity for roll-back.
But you might get an improvement with Refresh Window without needing to commit the record--it's worth a try.
And there may be design changes that would allow you to commit the record and still be able to "roll back" to previous data and state...
just another try:
give a object name to entire portal (like "portal_Adresses") and use the new function
RefreshObject ("portal_Adresses") instead go Commit
thanx everyone for the great ideas. i will definitively look into it. - i evaded refresh because there is a lot of cond. form. and it slows things down to much
but maybe just the single object might be fast.
(BTW i recognized that FM13 uses the discrete graphicscard whereas fm12 seamed not to do it)