Background:
I am using C1 XLS for .net with the backend of a vb.net 1.x asp.net website. On one page, a user can upload an xls file to the server. The site then uses the C1 xls component to access and retrieve the data in the xls file, processes each the retrieved row data and inserts the data into a database.
The Problem:
XLS files max out at 65536 rows. C1 XLS processes XLS files with approx. 12008 or fewer rows without incident. Files with more rows than this seem to cause C1 to lose track of the row and and it starts pulling in data from the first and other rows, corrupting the data.
Debugging Details:
I checked the XLS file after it's been uploaded but before C1 XLS starts reading it. The file is correct. Using watches and the debugger, I looked at the values in each row through the C1 XLS component - it is definitely reading data wrong after the 12008th or 12009th row. At first it goes back to the 1st row. and mixes data from that row with data from the correct row. Data for subsequent rows is pretty much all wrong - not merely from the wrong row, but also the wrong column as well. I am using v 1.1.20051.27 of the c1 xls.net product
Is there a fix or workaround?
Thanks,
Michael