Too Much Data For Report?

Bill_Feeney

Active Member
Hi All,
I need to create a columnar report as output to CVS that contains about 50 fields(obviously too wide to print). Every time I run the report it blows up.
I have tried to increase the width of the report using custom setting, but when I enter something greater than 21 for the width, it defaults back to 21.
Does anyone know how I can handle a report with this many columns?
The main reason for the report was as a quick and dirty way to export the data to Excel. Any help would be much appreciated.

TIA,

Bill Feeney
B7332 SP 13.1 Sun Unix Oracle 8.1.6
 
Hi Bill,
Can you please define "blows up"?!!
Here are a couple of features I have discovered in Xe...
If the report is only going to be run for CSV output, then the page size shouldn't matter - the fields can be placed outside the printable area, and they will still appear in the CSV.
What can cause a problem is if the fields are not spaced apart by at least 1 gridline, then some fields will not be displayed in the CSV.

Hope this is of some help,

Stewart
Customer: Xe/NT/Oracle
Office: B7331/NT/SQL
 
I was hoping for a bit more information.
Bill, can you tell me does it produce any output in CSV or the associated pdf that will have been created automatically?
If so, what does it look like, if not, is there anything in the log file?

Regards,


Stewart
Customer: Xe/NT/Oracle
Office: B7331/NT/SQL
 
bill,
try using the "database output" under the section menu. you can create an output file there.

RandyLlew
Kitchell Corporation

Hi All,
I need to create a columnar report as output to CVS that contains about 50 fields(obviously too wide to print). Every time I run the report it blows up.
I have tried to increase the width of the report using custom setting, but when I enter something greater than 21 for the width, it defaults back to 21.
Does anyone know how I can handle a report with this many columns?
The main reason for the report was as a quick and dirty way to export the data to Excel. Any help would be much appreciated.

TIA,

Bill Feeney
B7332 SP 13.1 Sun Unix Oracle 8.1.6
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OWDEV&Number=17556
 
Bill,

Yes, playing late...

Have you thought about doing a Table Conversion - instead of just a Columnar
report? If you TC to a CSV - it has the same affect as printing the report
to CSV(Excel). You can just click on the CSV and, providing you have
application extensions set correctly, Excel will pop open...

Yes! take into consideration that TC are not as flexible as reports... there
is some functionality disabled... or less 'enabled'.

We are using some TCs for EDI on records that exceed 1024 characters... hex
and all... I know it will work, I just don't know if that is what you want
to use...

regards!




Daniel Bohner
[email protected]
www.existinglight.net
JDE - XE & AS/400
JDE - B7331 & MS SQL 7x
 
I would like to thank everyone who replied with suggestions. I discovered, as did Denver, that with B7332 if the fields exceed the width of the output, even if CSV, the report gets an exception error (Blows up).
In the interest of time(had to have it done Friday afternoon) I just created a query in Access and output it to Excel...took 1/2 hr and worked great.
Being stubborn, I plan on going into JDE today and attempt a couple of the solutions offered.

Once Again, thanks.


Bill Feeney
B7332 SP 13.1 Sun Unix Oracle 8.1.6
 
Hi Bill,

I have custom report (B733.2, NT 4.0, SP 10) with a few fields that exceeding output area and we print that one (on enterprise, locally on fat client and locally on TSE) with no problem. Anyway, did you try to make report wide enough to accommodate all fields (my RDA can accept custom page width up to 21)? Or maybe to shrink fields. It’s won’t look nice but you are not going to print that.

Hope this helps,

Bojan.
 
I just tried to shrink each column to about 1 grid to enable me to fit all
the columns on the custom 21 wide output width. Ran the report to export to
CVS and it had the same exception and stoped running. Then I did a Hide
Section in the Do Section ER and got the same results.

I ended up creating a custom table with the fields I needed and did ER table
I/O to write to it. Then I linked to it in Access and output the query to
excel. This worked as well as the solution I did on Friday using Access
only.


Thank you all for the interest and suggestions in trying to figure this out.
Fortunately there are many ways to skin a cat.


Bill Feeney
JDE Technical Developer
B733.2, SP 13.1, Unix, Oracle 8.1.6




Bill Feeney
B7332 SP 13.1 Sun Unix Oracle 8.1.6
 
Back
Top