Axolot Data

Hi, I discovered what I believe to be a bug inTXLSWorksheet.InsertRows. To reproduce: 1) Create an Excel spreadsheet, populate cells A1 through A3 (ex: put in "Row1", "Row2", "Row3"), save as Book1.xls. 2) Create new Delphi project with code: procedure TForm1.FormShow(S...

Hi Lars, I'm still migrating code from XLSReadWrite and XLSReadWriteII 2.0 to XLSReadWriteII 5.0, and I came across a very difficult error to debug. After struggling for 6-8 hours, I believe I found the general cause, which appears to be due to the use of global variables. Our code in question makes...

Hi Lars, Again, I'm not hiding any exceptions. If an exception occurs in the OnReadCell event, for whatever reason (typically due to some bad data in the spreadsheet that the user created), that exception should bubble up... For an application with a UI, it should become an exception dialog (we actu...

Hi Lars, I believe you need to look at the code change I made again. It does not catch the exception, nor does it hide it. I added a try finally, to make sure that FManager.FileData.OPC.Close is called. If that call is not made, then the OPC is left open, thereby causing subsequent attempts to read ...

Hi Lars, I'm finally migrating my code from your old TXLSRead to TXLSReadWriteII5, and thus I'm using DirectRead=True. If my code throws an exception in OnReadCell, the TXLSReadWriteII5 component is left in a bad state. The next time the user tries to read a spreadsheet, they get an error: "OPC...

Hi Lars, We are finally upgrading to your XLSReadWriteII 5 (version 5.20.10... note that we bought 5 upgrade licences back in April, but we are only now finding the time to upgrade), and when I build with your source, I see some concerning compiler warnings. 1) [Warning] BIFF_ReadII5.pas(2906): Vari...

Hi, we are currently using Delphi 6 with XLSReadWriteII 2.02.35, and we are now in the process of migrating our code to Delphi 2010 (We bought licenses for 2010 2 years ago, but haven't had any time to use it. If and when we get migrated to 2010, we'll then probably go ahead and buy licenses for XE3...