Jump to content

Index on Global Fields


Jarno
 Share

This topic is 5754 days old. Please don't post here. Open a new topic instead.

Recommended Posts

If you wish to show the same related record for every record at hand use the carthesian product type relation, it doesn't need any indexing btw, you can start out with two dummy fields for the linking purpose, and then later get rid of them in both tables while the funtionality coninues.

--sd

Link to comment
Share on other sites

tanx 4 your replay, I know what you say but the problem is something else....

TAB A

- Global A = 1

TAB B

- Number = X

- Global B = 2

- Calculate = X + 2

I want this relation:

TabA::GlobalA=TabB::Calculate

This does not works coz Calculate cant be indexed coz there is a global value inside

it's stupid coz it is simple but real, and this is 1 of 3 very stupid things that FileMaker still have 'till v.8.5

Edited by Guest
Link to comment
Share on other sites

Just because you don't understand something, it doesn't mean it's stupid.

In any case, the solution for your example is very simple:

TABLE A

- Global A = 1

- [color:red]Calculate = Global A - TABLE B::Global B

TABLE B

- Number = X

- Global B = 2

[color:gray]- Calculate = X + 2

Relationship:

TABLE A::Calculate = TABLE B::Number

Link to comment
Share on other sites

tanx a lot, but you resolve the equation and not the defect of FileMaker.

the equation is only an example, if you want know the real calculate, it is as following:

[color:orange]Calculate = If(Global B = Number; 1; 0)

however, from you reply I understand that the "trick" is move the global field in master table from the related table ...but unfortunately it is possible only in 1% of the cases....

Link to comment
Share on other sites

The defect is not with FileMaker, but with your understanding of how indexing works. This is not a trick, it's just what's needed to get what you want. I don't think I've come across too many cases where having the filter on the parent side was a problem.

Link to comment
Share on other sites

Just because you don't understand something, it doesn't mean it's a defect either.

It doesn't matter where a global field is. The 'trick' is to move the "unstored" part to the parent side of the relationship. I think that should solve most of these cases, and there is a solution for the remaining ones as well - see here.

Link to comment
Share on other sites

This topic is 5754 days old. Please don't post here. Open a new topic instead.

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
 Share

×
×
  • Create New...

Important Information

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