Thank you for your post.
When adding records to a portal, you are linking them to the current record. If the current record is not saved/committed, then the portal records will be lost. Therefore, be sure to commit the record after each portal record is created. It could be done simply by a OnObjectExit script trigger on the last portal field displayed. That is, when you exit the last portal field, call a script that contains the script step Commit Records/Requests. This way, if FileMaker Pro/Go crashes while entering a portal record, all portal records will have been previously saved except the current one.
Warning, the Commit records step of this recommended technique loses the portal row focus. Once you have more rows than can be see without scrolling the portal, this method will "snap" the top portal row back into position and this will make editing data in the portal rows very annoying.
Many thanks Guys,
I have adding a commit record step on object exit for the last 2 fields the users are likely to use and I will see how it goes.
I guess it will be annoying if the focus snaps to the top, however at this point its a sacrifice I will have to make as the loss of data is frustrating for the end users.
There are alternatives, such as saving the current portal row in a variable and using Go to Portal row to return the focus to that row after committing.
And I'd be much more concerned about the crash than this loss of data from uncommitted records.