rindin Posted September 22, 2005 Posted September 22, 2005 I'm having a little difficulty trying to get something to work here. What I want to do is to perform a Find on a certain table and then switch to a different related table, and constrain that found set of records further. The problem is that when I switch to the other table, it shows all records, and not just the ones in my found set from the first table. Does anyone know of a quick and easy way to switch layouts to a new table and only view the records in your current found set? Thanks!
Matt Klein Posted September 22, 2005 Posted September 22, 2005 Found sets in FileMaker Pro 7/8 only apply to layouts using the same Table Occurrence. So, if you do a find on a layout and change to a different layout that uses a different Table Occurrence, even if that Table Occurrence's base Table is the same as the original layout, the found set will not be maintained. FileMaker Pro 8 introduced a new feature when using the Go To Related Record script step. You can now go to the related records for ALL records in your found set. Previously, you could only go to the related records of the current record. I imagine you would benefit from that new feature.
rindin Posted September 22, 2005 Author Posted September 22, 2005 Yes, it sounds like that would do the trick for me. I think I will just look into upgrading to 8 ASAP. Thanks!
Søren Dyhr Posted September 22, 2005 Posted September 22, 2005 Not that it has been entirely impossible before 7 or 8 checkout this download: http://www.kevinfrank.com/download/multi-gtrr.zip --sd
Matt Klein Posted September 23, 2005 Posted September 23, 2005 (edited) Good one Soren! Forgot about that. I didn't use that method much because of the 64K character limitation in FileMaker 6 and under. That method would still work even in 7/8 especially with the 64K limitation raised to 1 billion characters per text field. Edited September 23, 2005 by Guest
Søren Dyhr Posted September 23, 2005 Posted September 23, 2005 At the time when it came around existed 64K workarounds as well, but how it was done escapes me ...didn't Kevin mention it in his intro to the template?? --sd
Matt Klein Posted September 23, 2005 Posted September 23, 2005 He mentions it in his synopsis. He checks the field length and aborts the process if it is over the 64K limit.
Recommended Posts
This topic is 7059 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 accountSign in
Already have an account? Sign in here.
Sign In Now