One way to overcome this severer limitation in the way RBWIN does reports,
is to base the report on a temporary table. It will take some ingenuity on
your part to include the columns you need for beakpoints and all. But, it
usually can be done, but is an arduous exercise.
The other option, of course is to go to an odbc report writer. You may have
the same problems there too.
On my wish list is reports within reports in RBWIN, especially if the
sub-reports could be in break headers or footers, and be on independent
tables. Would be an extraorinary tool, if done right, fixing the existing
report bugs. Not a trivial undertaking, but a complete rethink of the whole
process.
-- Dennis McGrath
mailto:[EMAIL PROTECTED]
-- Tools for R:BASE programmers
http://www.enteract.com/~mcgrath/dennis
-- Full time consultant with SQL Resources
mailto:[EMAIL PROTECTED]
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Rich Young
Sent: Tuesday, August 14, 2001 6:43 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Multiple Reports Processing
Tom,
Thanks for your reply.
Append works in the dos report environment.
Using this technique with windows based reports will save the text to the
output file. However, all formatting (fonts, pitch, lines, etc.) are lost.
This application currently is written in RBDOS and I am in the process of
converting to RBWIN. I might have to re-think that !
Hope all is well.
Best Regards,
Rich Young
Advance Business Systems
10755 York Road
Cockeysville, Maryland 21030
(410) 252-4800
[EMAIL PROTECTED]
-----Original Message-----
From: Tom Grimshaw [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 13, 2001 7:14 PM
To: [EMAIL PROTECTED]
Subject: Re: Multiple Reports Processing
>>
Check out the APPEND parameter to see if it delivers the goods.
OUTPUT filename.txt
PRINT Report1
OUTPUT SCREEN
OUTPUT filename.txt APPEND
PRINT Report2
OUTPUT SCREEN
OUTPUT filename.txt APPEND
PRINT Report3
OUTPUT SCREEN
<<
