Niklas Nebel wrote:
Dave Calkins wrote:
I'd like to be able to export to an Excel file from my app which will be running in a shop floor environment on a machine which would not have MS Office or Open Office installed.

Why don't you just install OOo and control it using the API?

I don't have control over the machines on which our app is running, so the only thing I know for sure is that they'll have our app installed. Also, the machines on the shop floor running our app don't have a need for a full office suite, since they're collecting/generating the data and only want to be able to export to Excel for review later on other machines. Having them install OOo would probably be overkill. Of course, there's the option of including the OOo installation within our app's installation, but that would probably really grow the size of our installer.

For similar reasons we wanted to avoid the MS Office automation interfaces. Using them would require having the MS Office SW installed on the machine where our app was running and we couldn't ensure that either. Which is why we're looking for something to let us directly write the binary file format and OOo seemed liked a good possibility.

My hope was to be able to only include the code necessary to save the Excel file format. Then our installer doesn't grow very much, we're not asking them to install other software on the machines and/or we're not adding a lot of SW to the machines which isn't needed and wouldn't be used.

Would it be feasible to re-use the Excel file writing code from OpenOffice? I downloaded the OO SDK and was scanning the developer's guide, however, it seems to be coming from the approach of connecting to a running OO instance as opposed to re-using OO code in your own app (on a machine which wouldn't have OO installed).

If you really want to use parts of our source, there's a bit of an overview of the Excel filter classes at http://sc.openoffice.org/servlets/ProjectDocumentList under "Source Code Documentation". It's not completely up to date, but it might help to get started.

Thanks, I'll start there and see what I can find.

Dave


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to