-
Notifications
You must be signed in to change notification settings - Fork 299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
255 columns limit when reading .XLSX file #22
Comments
Hi @casbby, I don't currently know a workaround for this in LinqToExcel. It uses the JET or ACE database engine's which seem to both have the 255 column limitation |
Using this library I am impressed--thanks so much for contributing. I suggest you put the 255 column limitation (inherited from the database engine) in plain view on your intro doc page. Of course it's obvious when one stops to think about it upon unexpectedly encountering it. Nonetheless silence on this limitation when Excel itself supports over 16K columns is not good .... |
Ouch, @subsci, consider your attitude. This is a freely-available, open source project contributed by someone who didn't have to do it. It's hard to me that you could justify complaining about such a thing. It's a very kind thing that this is being offered at all. I notice that you don't have any open source projects you've shared of your own. Consider why that is and as a fellow human being, please consider the human being who has to read your comments. |
Hi,
I am trying to use the WorksheetRangeNoHeader method with the input parameters like ("A1", "CAA10000",1) as a workaround on the 255 columns limit on the provider. While this method works in a others' cases( http://social.msdn.microsoft.com/Forums/en-US/cf21f1be-d6e8-4ed9-b977-d6876bf0cf06/import-data-from-excel-file-into-a-datatable-column-limit). It is not working for linqToExcel.
do you have a workaround for this limitation?
Thanks
Casbby
The text was updated successfully, but these errors were encountered: