Not Empty validation change in FM7 portals?

[Gerry888]

Am I missing something here?

In FMP 6, if the user tries to tab from one portal row to another without having filled in all "Not Empty" fields, the validation-error dialog box will stop him and force him to fix the empty fields before moving to the next row. In FMP 7(v.3), "not empty" validation isn't checked until the user clicks out of the portal and commits the master record. The dialog box alerts him to the error, but the cursor simply returns to the relevant field in the first portal row, instead of to the row that actually contains the error. This is very confusing for the user, particularly if the error exists in a row he'd have to scroll down to find.

However, if a field's validation is set to look for unique or existing values, then the validation is done when the user exits the portal row in FMP 7, just as in FMP 6 (and I see it was "fixed" to work this way by FMP updater 7v2) -- so I have to figure the new behavior of the "not empty" validation is intentional. Is there some way to work around this, so the "not empty" validation is checked when the user tries to tab out of a portal row, like in FMP6? Or am I missing something really obvious here?

Thanks for any thoughts. --Gerry