Re: XLSX development from RPGLE

Not sure about POI.

Why don't you write some code to generate the XLSX files yourself ?

They are only XML files.

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT

----------------------------------------------------------------------

message: 1
date: Fri, 5 Oct 2012 12:51:30 -0400
from: Blake.Moorcroft@xxxxxxxxxx
subject: Re: [WDSCI-L] XLSX development from RPGLE

Hello all...

I'm wondering if anyone has taken the opportunity to build an Excel 2010 (xlsx extension) file using POI, as explained by Scott Klement.

We've been doing work with building spreadsheets directly and when doing conventional "xls" files we don't have any problems. But when trying to do the "xlsx" versions, we keep getting "terraspace" issues...I'm guessing some kind of method call with a null value but because the JVM drops out of the calling program immediately, all I get is a core dump which is next to impossible to analyze. We've done all the regular checks to verify classpath values and having the latest POI objects, but still no joy. I'm hoping someone else has tried this and run into similar problems so that I can get some pointers on what to look for or adjustments to make.

Have a good day.


Blake Moorcroft
Analyst/Programmer - Corporate
Farrow Group - Russell A. Farrow Limited
2001 Huron Church Road, PO Box 333, Windsor, Ontario N9A 2L6
Bus: 519-966-3003 ext. 566
blake.moorcroft@xxxxxxxxxx




Celebrating a Century of Excellence and once again named one of Canada's
50 Best Managed Companies!

This electronic message contains information from Russell A. Farrow Limited, Russell A. Farrow (U.S.) Inc., canadaplus.com or RAF Express Inc., that may be confidential or privileged. The information in this electronic message is only for the use of the intended recipient.
Inappropriate disclosure, copying, distribution or other use of the contents of this electronic message is strictly prohibited. If you have received this electronic transmission in error, please notify the sender immediately by return e-mail. Thank you.