There is nothing that springs to mind. I guess the obvious answer would be object serialization; so that all of the objects used in the creation of the HSSFWorkbook could be saved away to disc and then read into memory again when you need to continue processing. However, the API is not set up to support this as far as I know and I suspect it would be a major challenge to implement it.
Can I ask, why do you think that you need to write the workbook out part of the way through processing? Perhaps looking at ways to store the data you are generating until you can create the entire workbook may yield a 'better' solution. Yours Mark B PS Sorry but I still have not looked at th eimage loading issue. Have been caught up with Word bookmarks. Will play with some code lateer today. -- View this message in context: http://apache-poi.1045710.n5.nabble.com/Problem-with-inserting-images-after-saving-an-HSSFWorkbook-tp5710135p5710207.html Sent from the POI - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@poi.apache.org For additional commands, e-mail: user-h...@poi.apache.org
