Jump to content

FM7 v FM8 portals behave different


IdealData
 Share

This topic is 5720 days old. Please don't post here. Open a new topic instead.

Recommended Posts

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.

Link to comment
Share on other sites

This topic is 5720 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.