Related Tables in the same file

[Salesman0Gil]

Hello..

I have a file, with multiple tables in it.

I have some raw data in one table, and I want the summary in another.

I relate the two tables, with a common stock number. In the raw data tabel I have a Summry that is the Total of the raw data per stock number. I use Get Summary function to bring it in to the form. In the Summary table I just want Stock Number and the Summary Number.

I can not get the number to show up, I've tried setting things equal to raw data table, I've tried putting a field in the layout that would be the same thing etc....

Any ideas?

[Walter B]

Do you have an actual record in your summary table that relate to records in your raw data table?

BTW, depending on the size (record count) of your database, your method may not be the most efficient way to go about this one. But we can get to that afterward.

[Salesman0Gil]

Yes..

It is an invoice/inventory file. That runs on Stock Number

The Raw Data is the Quanitity of Stock Number, summirized by total Quanitity by Stock Number.

The Summary table has a list of Stock Numbers, that I was hoping to keep the quanitity in. So I can say so far this month I used 34 ABC.

[Salesman0Gil]

After tweaking it for a while I got it. I was using a second instance of the same table, and that would not work. Why not?

I am curious though of a more effcient way.

[Walter B]

Each Table instance is its own entity, I'd have to guess that the relationship was between the table 1 and and the first instance, and that why the calculation wouldn't work.

Efficiency is somewhat a matter of perspective. If you're deal with a small database with few records, the programming I'm about the suggest is probably more work than it is worth.

Every one of the relational calculations you've created has to run through the database everytime you bring up the layout they are on, and regardless of whether any changes have occurred on that item. By their very nature calculated numbers is not generally saved or indexed. On a database with a large record count this cause a performance problem.

I have found that using looping scripts with calculations, you can set the number (indexable) in the summary field, and greatly improved the processing and display time. And you have control over when the updates happen to your summary fields and with a properly written script bypass records that do not require an update.

Hope this helps