Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I need to read XLSX files and extract a maximum amount of content from it. Which of the API’s should I use?
OLE DB, open XML SDK, or Excel Interop?
You can try all of them and choose the one that fits you most…
Depending on data you want to read, I’d suggest you to use Open XML over Interop or Ole DB.
I don’t know an open XML SDK, although I’ve some experience with EPPlus library which I’m using a lot and can say only good words about it – it’s fast, easy to learn, with good examples. The library is basing on Open Office XML format, so I suppose it’s pretty much the same as the SDK you’ve mentioned, and is capable of easy read and write Excel 2007 and 2010 files.
On the linked web, you’ll find a library itself, documentation and some example “Hello World” projects to download.
Why that library in the first place? Because with it you will be able to read not only cells values, but also their colors, fonts, widths and heights, merging and all that detailed stuff, that you can not only read, but modify as well. What’s more, you don’t need the Excel installed to do that.
On the second place – just in case you need to extract tabular data from worksheet – you may play with OLE DB. I’m afraid with that you won’t be able to extract any info about formats, colors etc., as well as the data must be in a tabular organized worksheet, so you can treat is as a database’s table.
The last one is Interop, because:
– it’s a COM library, so you need to be very careful when playing with it via .NET, as it’s easy to cause some ugly and hard to find memory leaks (confirmed by myself bad experience) – if you don’t dispose their objects properly, it leaves the Excel.exe process opened,
– it’s much slower than previous methods,
– basically, it has almost no more added value that one of the previous methods (EPPlus or OleDB) and requires Excel to be installed on client’s machine, so why to use it?
Good luck, then.