Yes, I thought that might be the case. The better option IMO *is* to use POI as this will allow you to write an application that can be run on any platform, will be robust and run quickly as you are manipulating files rather than applications. Even though it is likely to be a fairly involved process to copy all of the attributes of a cell between workbooks, you will only have to write it once. Converting the xls files into xlsx ones using OLE/COM is an additional step you would have to undertake for every file you process, will restrict you to running on a Windows platform as COM is a Windows technology of course and it will run fairly slowly as you would be controlling an instance of Excel.
One possible approach I did not mention is to use OpenOffice and write what is - or at least was - termed a UNO Client Application. If OpenOffice does now support writing the xlsx file format, then you can work entirely with it. UNO is quite complex as it relies on an approach where you ask managers for objects that provide services. This complexity was deemed necessary to support a varety of different programming languages. Using OpenOffice means your application would be platform independent but it does demand that you install OpenOffice wherever the application is to be run. Somewhere, I have a simple UNO application that performs file conversions; if I can find it, I will post the code so that can see the type of thing I am talking about. Also, I will look out the JACOB and SWT code that I wrote and do likewise with that, again once I can find it. -- View this message in context: http://apache-poi.1045710.n5.nabble.com/Cast-HSSFRichTextString-to-XSSFRichTextString-tp5711676p5711682.html Sent from the POI - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
