Hi,
I'm trying to load an Excel file and the Load function through an exception 'Attempted to read past the end of the stream'
It is an Excel 2003 file and I can open it using Excel.
Thanks for your help,
hi,
I have downloaded the lastest excel dll (Infragistics4.Documents.Excel.v11.2 - Version 11.2.20112.1010) from Infragistic webiste but I am still getting the same error message for the one of the file.
May I know the reason or root cause of this issue?
Thanks,
I was actually responding to the previous post by RedRag. I didn't see your post when I posted my reply.
My guess is that there is some feature in your Excel WorkBook that we currently cannot support. But it's certainly possible that there's a bug here that needs to be addressed.
But without being able to duplicate the issue, I can't even begin to guess what that might be. Is there any way you could create a sample Excel file without the proprietary data in it so we can test it out?
Mike -
You misread my earlier reply. I stated:
"No, the spreadsheet is not password protected."
To clarify:
The spreadsheet that we're having this issue with is NOT password protected.
That explains it, then. We currently do not support loading Excel files with password protection.
I recommend that you Submit a feature request to Infragistics
I apologize for the late response, I've been away.
No, the spreadsheet is not password protected.
This situation happens when a client who has an Access 2003 database exports a saved query to an Excel 2003 file. The data is in this spreadsheet is confidential, so I can't post this file directly.
If we open the exported file in Excel and save it as is (with no changes), then the Load() method works.
I also tried this export under Access 2010 with the same behavior: Load() fails with the same exception.
For now, we had to convert to a text file export to get around the issue and we're not using the Infragistics Excel Load() function for this processing.
If there are other users experiencing this issue and Infragistics wants to determine a fix, I can attempt to strip the confidential data out and produce an Excel file that illustrates the issue.