We're just testing 7.6 and I'm hoping the improvements to the Compound Reports will be helpful. I'm trying to make a correlated compound report and I'm getting this error message:
(FOC3296) Error found in Coordinated Compound Report: At Component report2
(FOC3303) Compound report COMPONENT out of order

I haven't been able to find any further explanation as to what this means.

What's happening is that I'm getting 2 sets (not correlated) of the first report output and nothing from the second report.

Bethany

This message has been edited. Last edited by: Kerry,

What release of 7.6 are you testing with. I found this for message FOC3303:

Summary: PDF Layout (FOC3303) Compound report COMPONENT out of order
Case: 31832011 Product: Developer Studio
Status: Submitted to Product Division Date Reported: 07/13/2007


Environment Detail Information

Product Release Gen Level OS
Reported in: Developer Studio 7.6.1 WIN/XP


Problem Detail Information


Description:

PDF Layout (FOC3303) Compound report COMPONENT out of order
PDF Layout Painter tool will error with procedures that ran under DEVSTUDIO
7.14

0 NUMBER OF RECORDS IN TABLE= 0 LINES= 0
(FOC3296) Error found in Coordinated Compound Report: At Component report1
(FOC3303) Compound report COMPONENT out of order
Compound Report is TERMINATING.....
Workaround:

none

It is possible, if you did the 'reports' in separate fexes, that you could create a new PDF Layout Painter focexec and redo it. Maybe that would help.

BTW, if you ever want to get further information on error messages, go to the Advanced Search link in the upper righthand corner of this page, log on, then go to Search and type in the error message number. That is how I found the above information.

At any rate, it looks like you might have to open a case or get a higher version of 7.6. We went from 5.3 to 7.6 and skipped 7.1.x altogether so didn't run into the problem.

I was just researching this error myself, and although this did not help my search, I was able to determine that the cause of the error for me was that while using the GUI, the application stripped the default TABLE request from the initial COMPONENT. I continued to add sub reports and did not notice in the code that it was missing.

I finally foun dthe hole, and added in the following code:

 SET COMPONENT='report1'
-*component_type report
TABLE FILE SYSCOLUM
" "
SUM TBNAME NOPRINT
IF READLIMIT EQ 1
ON TABLE SET PREVIEW ON
ON TABLE SET PAGE-NUM NOLEAD
ON TABLE PCHOLD FORMAT PDF
ON TABLE SET STYLE *
object=line, position=(-1 -1), endpoint=(-2 -2), $
END 

It now works like a charm....

Hope this helps...