Show a Control with array data on a Report after query is complete

[talktozee2]

Hi, everyone.

My problem is a bit too complex to explain in writing, let alone in the title of my post, but I'll give it a shot.

I have a report that has a basic set of columns and rows, but complex calculations are run between cells of each row, and between cells of different rows. Based on these calculations some rows are hidden and some are not.

Now, I need to temporarily store paired data ("date" and "amount") from some of the rows until the query that feeds the report is done, then run some calculations on the stored data, then show that data in a control that appears on the report after all of the rows are displayed AND the control can't impact the placement of the rows (meaning the control has to "overlap" any existing rows and not push them out of the way).

Thoughts? ;) I had thought of a sub-report, but I still need to grab and process the data from the main report on a row-by-row basis.

[talktozee2]

Ok, I've stored the data in a temporary table, but now I need to display the data in the "acDetail" section WITHOUT it repeating X times for each row of data. Anyone?

[Stewart Ross]

Ok, I've stored the data in a temporary table, but now I need to display the data in the "acDetail" section WITHOUT it repeating X times for each row of data. Anyone?

If I understand correctly, your temporary table has repeating data rows and you need to display them on your report without the repetitions. One simple approach I can think of is to group the rows on whatever criteria suits the data (and I can't say what because you have not shown us a sample of your data), add a group footer to the innermost group of the criteria in your report, then put your report's textboxes etc not in the detail section of your report but in the group footer. The grouping will take care of duplicates automatically. You can close the width of the detail section down to nil as you won't have any controls in it at all.

I am assuming that your temporary table is intended to reduce the processing needed at the report stage, otherwise use of the group footer approach may not help you if you need to do further processing at row level in the report.

-Stewart

[talktozee2]

Stewart, thanks for the response.

I'm sorry, my description of the problem was a bit imprecise.

What I'm really trying to do is get the data in my temp table to appear in the acDetail section of my report WITHOUT pushing down the rows of data that are shown in acDetail. This needs to happen as the data in acDetail is grouped by a field, and the data in the temp table is related to each section of acDetail that's grouped. I believe I need to come up with an entirely new approach and use Headers and Footers as they're meant to be used.

Basically, I'm trying to create a left-to-right AND top-to-bottom report, where my temp table is on the left and my rows of data are on the right, and each of these groups of data are segregated.

Any thoughts on the proper structure? I know I'm close, but am unfamiliar with proper Group Headers and Footers to get the report just right.

[Stewart Ross]

...
Basically, I'm trying to create a left-to-right AND top-to-bottom report, where my temp table is on the left and my rows of data are on the right, and each of these groups of data are segregated.

Any thoughts on the proper structure? I know I'm close, but am unfamiliar with proper Group Headers and Footers to get the report just right.

Hi talktozee2. If you could post some sample data it would really help with visualising how to do the transform (if it is possible). In particular, a short extract of the report's source data as provided in your intermediate table, and an extract of how you visualise it after processing would be really helpful. This is one of those occasions when we cannot go further without knowing some of the details of the fields and the row structure involved.

Happy to advise further in due course...

Cheers

Stewart