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.

Unique value validation has changed in FM 7!

Featured Replies

Hi,

I have used customer postcodes and field that required a 'Unique' postcode field value during data entry to avoid creating duplicate customer records on my database.

This worked well with FileMaker versions 3 and 4.1 but with FileMaker 7 the onscreen warning of a duplicate does not trigger until I have finished keying-in all the address and customer data. Earlier versions of FileMaker picked up the duplicate as soon as I tabbed out of the postcode field.

I'd appreciate advice if anyone knows a simple way to get round this? It still seems to work in the 'old way' in FM Dev 7 in Windows XP... but not on the Mac in OSX!

I'm using FM7 on OS X, and it works properly for me. Have you updated the mac side to v 7.02? I think they changed it back in that revision.

  • Author

Thank you for the information - I'll check the update now.

  • Author

It now works perfectly!

Thanks again

I'm rather new to filemaker but love the abilities it has ..

I'm trying to create a database that I can use to dedupe sales leads,

this Unique Value Validation sounds like a good possiblity could you please let me know what you think and if it is a possibility how I would use it ..

Rob

(MNC-Man)

Rob,

It sounds like two separate items: getting rid of dups and preventing new ones from occuring. To find the dups, enter find mode and put a ! in the field that you want to dedup from. That will give you all the duplicate entries for that field. Be careful, though, if it is a name/address type table. Joe Blow could be Joseph Blow in another record. While a dup, it wouldn't be picked up. You can certainly author scripts to help recognize dups.

The larger question is how to prevent new dups from happening. You need to have a unique field, such as SSN or something. Put the validation on that field and you will eliminate dups.

Thanks alot for the tip It has helped alot..! Now is there away to do the same thing but between two databases that have related filed ?? this would be the more important part of the solution..!

thanks in advance..

Rob (MNC-Man)

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.