Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×
The Claris Museum: The Vault of FileMaker Antiquities at Claris Engage 2025! ×

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

Recommended Posts

Posted

Which is faster in 7...basing a relationship on a calculation field in two tables that concatenates two fields or basing a relationship on those two fields simultaneously between tables as you now can in 7? This will be for very large databases (many millions of records) so speed is very important.

Posted

Which is faster in 7...basing a relationship on a calculation field in two tables that concatenates two fields or basing a relationship on those two fields simultaneously between tables as you now can in 7? This will be for very large databases (many millions of records) so speed is very important.

Posted

Which is faster in 7...basing a relationship on a calculation field in two tables that concatenates two fields or basing a relationship on those two fields simultaneously between tables as you now can in 7? This will be for very large databases (many millions of records) so speed is very important.

Posted

I would think using the individual fields would be faster. But if both calculations can be indexed, then the difference may be negligible. Of course, there is no reason to create the concatenated fields since you can use the multi-criteria relationship and also save a lot of file space, especially over millions of records.

Posted

I would think using the individual fields would be faster. But if both calculations can be indexed, then the difference may be negligible. Of course, there is no reason to create the concatenated fields since you can use the multi-criteria relationship and also save a lot of file space, especially over millions of records.

Posted

I would think using the individual fields would be faster. But if both calculations can be indexed, then the difference may be negligible. Of course, there is no reason to create the concatenated fields since you can use the multi-criteria relationship and also save a lot of file space, especially over millions of records.

Posted

Hi,

The only resistance of a compound (concanated) calculation is when one of the key of this compound can be empty.

You can search for a Matching ID where the second key is empty with a compound calc.

Posted

Hi,

The only resistance of a compound (concanated) calculation is when one of the key of this compound can be empty.

You can search for a Matching ID where the second key is empty with a compound calc.

Posted

Hi,

The only resistance of a compound (concanated) calculation is when one of the key of this compound can be empty.

You can search for a Matching ID where the second key is empty with a compound calc.

This topic is 7251 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
×
×
  • Create New...

Important Information

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