Hi everyone! Here is my problem

I have a database working in FMP 4.1, and in this one I have to files with a relationship. I use a portal to view the records on the other one, and below the portal i put the fields to resume the results of the portal. For this fields I use a lookup of the subsummary fields of the records beeing displayed on the portal. In FileMaker 4.1 this works fine. I mean you can make a lookup on the subsummary fields of another file, if you sort the records found correctly.

When I changed in FM7, something strange happened, the lookup was working again but instead of showing the subsummary of the records beeing browsed, it showed me the total subsummary of the all records of the file! And I can't find a solution to put it right.

Someone could say to use a relation instead of lookup, but I want to use a lookup because it speeds a lot the calculation, it makes nearly 7 to 8 time faster.

Any help on this? Hope I have explained it right. Thanks Toni

Have you tried the getsummary function in the related table rather than the summary?

Yes I've tried with the getsummary too. In fact that was the first thing I thought, sure it would have worked, but no result.

In FMP 7 you have an auto-enter option to use a calculation. Have you tried that? You could use the aggregate functions with the relationship in the portal. Then sorting of the related records would not be required.

He he, it worked! Thanks Ralph, I'm gonna do some more testing, but it is going to work for sure, thanks again.

Your welcome. Glad it worked.

Here I'm again with this problem which was solved with the autoentry option. After working on the database, yesterday I noticed something never seen in previous versions. So in the previous if you want to lookup on a subsummary field on another file, you need first to call the records for whom you want to lookup the summ.

But with FM7 you don't need this. FM7 will do the summ of the records you need using the value of the reference field you use to create the relationship between files. This is new and I think it is nice as an option. The only problem is you can't relookup if something has been changed in the file. But not much of a problem. I created a script which first will delet the record and then recreate it, and the new one will have the updated values.