Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Plagued by "This record cannot be modified..." err

Featured Replies

After converting 20 files to FM7V2 from FM5.5V2 without any errors (no problems in the log), I am pulling my hair out trying to close/hide windows that I don't think are open trying to get a simple script to work in V7. Following is the script from 5.5 which is run from my "Visits" file. The purpose is to pass values in a "Global" file for reference in a yet to be opened file. (I have read that V7 can do some passing of values somehow, but I haven't played with that yet.)

Set Field ["Global Link", "1"]

Set Field ["Global::Client ID", "Client ID"]

Set Field ["Global::STR1",""""]

Set Field ["Global::STR2",""""]

etc.

The V7 converted script (that doesn't work) follows:

Set Field [Visits::Global Link; 1]

Set Field [Global::Client ID; Visits::CLient ID] *

Set Field [Global::STR1; ""]

Set Field [Global::STR2; ""]

etc.

The * notes the script line that causes the problem. I have tried adjusting, closing or hiding the Visits window with no effect. Every time I try to set a field in Global file from a field in Visits, I get the following error:

"This record cannot be modified in this window because it is already being modified in a different window".

How on earth (or at least in V7) do I get this stupid thing to work?

Set Field no longer automatically commits the record, removing the record lock. The reason being it will be more efficient when you have a series of Set Field script steps to just commit the record once.

You probably have an uncommitted Visits record from a previous script.

You should add the Commit Records/Requests script step after every series of Set Fields (and any other record modification, like cut and paste), to all scripts.

Thanks for this reply you have confirmed my thoughts / question in another post (FMD6 to FMD7 migration help). This commit record issue is a bit of a catch on initial conversions. Not a problem once understood but is hard to find desciptions of this obvious trap in the migration docs (or may be I just cant read)

Thanks

Tony

It's in the FM7 Migration Foundations and Methodologies white paper somewhere, but it's understandable if your attention drifted off and you missed it That's a heavy read.

Page 75

  • 2 weeks later...

Can yuo elaborate on the source doc? Where do I get it?

Create an account or sign in to comment

Important Information

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

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.