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.
Juggernaut

Featured Replies

This is probably simple but I'm struggling to figure it out....

How do you create a deletion rule which prevents a user deleting a parent record if it has any children thus avoiding the possibility of orphaned records?

I guess it involves the "when deleting a record in this file, also delete related records" checkbox in the edit relationship popup however as far as I can see checking it will result in parent and child both being deleted and leaving it blank will result in orphans.

I'm looking to implement a solution that forces the user to delete any existing child records prior to being able to delete the parent.

Any advice much appreciated.

Iain

You set all passwords except for the master to Edit Only in File->Access Privileges->Passwords. Then you script all deletions, testing

If [relationship::constant]

Show Message ["You must first delete child records yadda yadda..."]

Else

Delete Record/Request [No dialog]

End If

where constant is a calculated field always equal to 1. If you don't have a constant, use If [Length( relationship::serial )].

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.