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.

Upgrade problems from FM4

Featured Replies

  • Newbies

Hi,

First time to this forum so please forgive if I have posted in the wrong area.

The problem I have is a runtime that i wrote 10 years ago in filemakerpro v4.

I need to upgrade to the latest filemaker and after purchaseing filemaker 8 advanced i opened the filemaker 4 files and followed the prompts to update to filemaker 8. After doing the automatic conversion the following errors are occuring.

1. I keep getting "can not modify that record cause it is open somewhere else" from my browse around this forum it looks like i need to put commit record script step in my scripts but am not familiar as to where i put this step in my scripts.

2. bad relationship error which totally locked up the runtime (had to kill the task to get the computer back). I found the offending relationship and deleted it but now some of my calcs dont work.

It seems filemaker 4 is much more forgiving with the types of relationships created.

Thanks in advance,

Brad

For more info about the "the record is open somewhere else" you should read Ilyse Kazar's "Record Ownership" article (page 74) in the big "migration_foundations.pdf", which is on FileMaker's site. Many things about "record-locking" are different in 7/8. She explains it well, with charts to show the differences.

In your particular case my guess is that you are editing related records, then finding that the parent record is locked. You need to commit either the parent record, or the child records to release the lock (depends on how/where you're editing them). In general you should commit records after editing them (you only need to commit once at the end of a Loop however, unless a contained step, such as a Go To Related Record [] or Lookup requires it sooner).

There are several reasons why, but one is the possibility of multiple windows, where even the same person could try and have the same record open in 2 places, which isn't allowed.

(P.S. I moved this thread to Upgrading & Migration. It's not really a "Developer" topic so much. Doesn't much matter, as most of us just read as "Recent Posts")

Edited by Guest
Moved thread

  • Author
  • Newbies

12.4MB sheesh

OK, thanks for the tips, i'll go read for a while :

I had trouble finding the file, for those that may look here in the future I found it at http://www.sofa.on.ca/files/migration_foundations.pdf

Regards Brad

Create an account or sign in to comment

Important Information

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

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.