Jump to content
Sign in to follow this  
Marc .

Relationship based on "≠" - Bug in FMP 9

Recommended Posts

Hello there,

I'm not sure it is actually a bug, but I've found that When you define a relationship based on "≠" or "<>" FileMaker 9 behaves differently from 8.5

An empty field will no longer be considered different from a field with a content. It means that you always need some content in a field to trigger the relationship.

Can anyone else duplicate this=

It it a bug or just a change in the engine?

Share this post


Link to post
Share on other sites

Hey Marc,

Can you supply a simple example file for us to compare?

Share this post


Link to post
Share on other sites

Marc, I am pretty sure that this is always how the not equals relationship worked. If you don't have a value in the field, you can't have a relationship based off of it. I tested this to make certain that there were no changes and it appears to work the same in 8.* as well as 9

Edited by Guest

Share this post


Link to post
Share on other sites

An empty field will no longer be considered different from a field with a content. It means that you always need some content in a field to trigger the relationship

I'm with Ender and Sixfried here, it have laways been that way.

--sd

Share this post


Link to post
Share on other sites

I think we/you need to clarify which direction you're going. The originating side must have a value, whether you use equal or not equal. But the targeted side does not need a value to be found with not equal; empty matches not equal in that direction. Seems the same in 9.

NotEquals.fp7.zip

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

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