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.

Can one limit the "!" (find dups) to the current found set?

Featured Replies

The ! operator in find mode identifies duplicates in the entire table, regardless of using "constrain found set" in find mode.

 

Is it possible to limit its scope to the found set?

 

Or achieve the same with a simple work around?

 

thanks

What about finding after having identified duplicates ?

  • Author

That does not work in this case.

 

I need to select cases based on varying criteria, which may or may not eliminate some duplicates depending on the specific requirements.

 

Then I need to see how many duplicates remain under those circumstances.

 

If I find dups (with !) first, then start to filter, I get a mix of dups and non-dups, which I can only remove with a new "!" find, which does not work since it uses the entire table, not the found set.

 

The ! operator in find mode identifies duplicates in the entire table, regardless of using "constrain found set" in find mode.

 

Is it possible to limit its scope to the found set?

No.

 

 

Or achieve the same with a simple work around?

 

You could summarize the found set using a summary field to count the size of each group. Any group whose size is > 1 is made up of duplicates.

Can you use !criteria in your find?

The ! operator in find mode identifies duplicates in the entire table, regardless of using "constrain found set" in find mode.

 

Is it possible to limit its scope to the found set?

 

 

I have found this behaviour frustrating too!

 

A workaround I have found, is to remove the index for the field you are searching..  To do this, go to Manage Database, go to Storage:  Where it shows "Indexing", click the "None" button AND make sure Automatic creation of indexes is turned off.

 

In many cases, indexing isn't an absolute necessity, and this workaround will work.  (I'm aware there are exceptions).

 

Regards

Ralph Learmont

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.