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.

Going to All Related Records from a Big File

Featured Replies

I have a master file of companies and a related file of employees. How can I go to the related employees of ALL the companies in the found set of the master file?

My problem is that the master file is large, 10K records or so and will grow.

In most cases I would set up the following:

1) Go to a layout in the master file that contains only the Company ID number.

2) Copy all records

3) Go to a layout containing a global field that will act as a temporary match field to the Company IDs in the Employees file.

4) Paste into that global field

5) Go to related records in Employees (via the global field).

That has worked wonderfully in the past. However, with a master file of potentially 10-20 thousand records, would this method not run into the problem of 64,000 allowable characters in a field?

How do I get around this? Is there a much better way?

--Thanks,

Dave

  • Author

P.S. --Forgot to mention that this is to be a multi-user system on a network, so I would like to avoid having to mark the employee records and tie up the system....

The only other way I can think of would be to loop through the found set of companies and go to the related employees of each one, marking the found set of related employees. When the loop is finished, go to employees and find all marked records.

Since it's a multi user setup, have three fields: gCurrentUser which is a global field that is unique for every user on the network, Mark, which is a number field that you actually mark, and gloalMark which is a calculation field that is set to the gCurrentUser if the Mark field is marked. Then search the globalMark for the gCurrentUser to find the related records.

Chuck

  • Author

Interesting idea about how to mark the employess. Only thing is, using that original Mark field would still necessitate that other users not be editing any of the desired records --or using the Mark field themselves. At least I believe this is so.

Any other ideas?

Thanks,

Dave

Let's see. Instead of using a mark field with a value of 1 or 0, use a text field. You still have a global field with the current user's name (must be unique). To mark the field with the user's name, set it to:

Case(

quote:

Originally posted by Dave Bud:

However, with a master file of potentially 10-20 thousand records, would this method not run into the problem of 64,000 allowable characters in a field?/B]

Will your found sets be that big? I cannot imagine them being that large, if so, you should be doing your finds in the employee file.

Assuming that you have an ID that is somehow unique (say Name or Number) and it is 10 characters (10 bytes). You can have 6400 in your found set without running into the problem.

Now if you think that this is the case, then perform these finds directly in the employee file, or save the find criteria into some globals so that you can run the same find in the employee file.

------------------

=-=-=-=-=-=-=-=-=-=-=-=-=

Kurt Knippel

Consultant

Database Resources

mailto:[email protected]

http://www.database-resources.com

=-=-=-=-=-=-=-=-=-=-=-=-=

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.