FM7 v FM8 portals behave different

[IdealData]

Heads up folks.

Recently I did some work in FM7. Basically I had scripted entry in to the fields in a portal to allow editing of existing data but prevent new records to be entered at the bottom of the portal. (New entries were handled in a different way to ensure data integrity and the relationship had to support creation in the related table)

The script tested the current row against the LAST value for the relationship to allow/disallow editing.

Then I ran it in FM8...

Each time I clicked on the fields the script would exit against the test. I discovered that FM8 does not get the current portal row number until a field had been selected, whereas previously the current portal row number had always been available immediately.

I adjusted the script to ensure entry into the appropriate field and then performed the test - everything works.

None of this was difficult to do (although it gave me a fright for an hour) - but it's a "heads up" for those of you doing conversions.

[Ender]

Yes, there are a few changes with focus on portals in FM8. See this thread for one about aggregate functions:

http://fmforums.com/forum/showtopic.php?tid/171699/