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.

Which is faster in 7...

Featured Replies

  • Author

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.

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.

  • Author

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.

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.

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.

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.

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.

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.

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.

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.