Jump to content

Performing Finds on Portals


Pedro
 Share

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

Recommended Posts

You actually never need to. Searches in portal rows search the main file and not records in the related file. If you need to find records with no related records, create a field in your main file defined as "Count(Relationship::Any Field)" and search for zero.

-bd

Link to comment
Share on other sites

Searching portals or related fields also forces FM to create a “temporary” cross-file index, which, with lots of records takes ages – don’t do it! That’s the rule here.

Rigsby

PS: There are lots of tricks to get around this problem – but to help, we would need more information.

Link to comment
Share on other sites

I’m not quite sure where you got the information that there is no such thing as a “cross-file index”! This term comes from Filemaker itself, not from me. If you search a portal, you are right, FM uses the index from the related file and the search performs pretty much as though you performed it on the file itself. However, if you enter search criteria in a local field and in a portal, FM has no constant index for this search, and thus creates a cross-file index. This problem is explained fully on FM’s homepage in the technical area, and touched on in Scriptology from Petrowsky & Osborne. Test this – create a calculation field that joins a value from file A with a value from file B, then enter search mode and try to paste from the index!!! No way – can’t do it, because there is no index.

Rigsby

Link to comment
Share on other sites

This topic is 7331 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.