Hello Srini, POI writes Excel files which are clearly different (at a binary level) from those written by Excel and sometimes these differences cause bugs (applications failing to read POI generated files properly). If I have understood correctly, you have said that Excel reads the file OK but MS-Access does not. Priority is given to fixing bugs which cause files to read incorrectly in Excel. It also sounds like you have a work-around (just add an extra column and ignore it later). Having said that, if you're able to help with some more investigation, we might be able to find a fix.
You don't seem to have stated explicitly whether creating the file manually/directly with Excel causes the same problem in MS-Access. While this seems very unlikely, if true it would imply that the problem is entirely within MS-Access. On a similar note - what happens when you re-save the POI generated file with Excel? Can MS-Access read it properly after that? There are a few more details that might be important: Are you using HSSF or XSSF? In MS-Access, are you using the workbook as an ODBC Datasource, or are you just doing an import (converting Excel sheets to MS-Access tables)? What about boundary cases - how does MS-Access behave when POI writes a file with 3,2,1 or even zero columns? regards, Josh --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
