Hi,

TableA (f1 , f2 ,f3 ,f4 ,f5)

TableB (f1 , f2 ,f3 ,f4 ,f5)

RelationshipA: TableA::f1=TableB::f1

AND TableA::f2=TableB::f2

AND TableA::f3=TableB::f3

through a portal on a TableB layouy I am trying to get how many instances there are of X (or any other kind of aggregate function).

X is a value of,lets say, TableA::f1

I need for each X in TableA::f1, its number of instances in the portal.

Basically with sub-summary report you can get these results because of the use of grouped data.

But I need to export these numbers, so the sub-summary report is useless to me.

I found a way with exporting and then importing back but I don't like it : - its to complicated.

Any Ideas of how it is possible through a portal?

or any other way...

I guess its not possible then...

As I have a lot of calculation on FNP in order to perform this kind of action (million records) I think I'll move the data to mySQl...and run the queries from FMP...

I guess its not possible then...

Maybe - and maybe no one understood your question. I know I didn't.

About the only thing I did understand was this:

Basically with sub-summary report you can get these results because of the use of grouped data.

But I need to export these numbers, so the sub-summary report is useless to me.

But you can export summarized data directly.

OK... i'll explain it in a simple way

How can I use the results of the sub-summary report?

For example if I want to build a graph from these results...

If you have a table with fields:

Category

Value

sSummaryField

and you sort the records by Category, you will get the option to group by Category when exporting (see screen shot).

More detailed instructions can be found in Help > Saving, importing, and exporting data > Exporting data from FileMaker Pro (para 9, Export grouped summary values instead of individual records).

I know about the export work-around...

I just wanted to avoid it and not to work with more exported files...

Bt I'll guess it will do...

I just wish I could get these results somehow through a portal...

It's possible to get a summarized portal too - but I don't understand your structure well enough. Perhaps you should post a simple demo file.

How is this supposed to help in building a graph?

If I have in a portal:

a 1

b 2

a 3

c 4

c 1

Then I need the following results from my portal:

A 4

B 2

C 5

in other words: grouped data.

This simple to to in portal when you have a simple relationship...But what if you have a relationship with 10 matches??

Can you present the entire problem, from A to Z?

First you said:

But I need to export these numbers, so the sub-summary report is useless to me.

Then you said:

I know about the export work-around...

I just wanted to avoid it and not to work with more exported files...

Now you say you want it in a portal - but you also say you want "to build a graph from these results". I believe these are two separate things.

If we don't know what you have and what you need, we cannot help you.

Here is an example file....

for example, when you open the file for the first time, how do you get Moshes and Daves summary separately?

test.zip

I can think of several ways to do that - it depends on the purpose. I can see no purpose in aggregating customers by name. You have, once again, presented an abstract problem. In a real solution, there would be a table where each customer has a unique record, so we would use that.

You are taking about managing Customers and I am talking about managing sales...

The data in the file is made up ofcourse...

If you think of a Table with flights (passenger name, flight cost, destination),

and you want to know the top ten frequent fliers to USA in May?

or in the example in the file:

If I want for each customer his total buyings in a specific period of time in a certain country?

you can go and run a loop for each related value..but what if you have hundreds of thousands records???

In your example, the sales table was labeled Customers - and there was no Customers table. If there was one, you could have set up the global conditions in it. Then each customer record would look at filtered sales, and another table could look at filtered customers. And all that would give us is a view for someone to look at.

Your flight example seems to me a different problem altogether, so it would probably require a different solution.

This is getting tiresome, so let me put it this way: there's no one-size-fits-all solution that I know of. It seems that every time you get a solution for an abstract question you turn around and say 'but the real problem is different'. I am tired of playing this game.

the problem is still and always been the same: to get grouped data from a portal...

nothing was changed.

I do not want to do it with export because this is a multi user solution and importing back the data can be very confusing when more then one user are running it (the script) at the same time....

SO..my dear friend.... nothing was changed ???

Edited May 4, 200718 yr by Guest