Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Depending on the features of Excel you need you'll need to install Excel on server or the client, or a third party control(s) that understand the format.</p> <ol> <li><p>If the application is WEB application where the application actually showing the data locally on the client via a web brower : See this MS link : <a href="http://support.microsoft.com/kb/162059" rel="nofollow">http://support.microsoft.com/kb/162059</a>. Here you're actually sending the xls file/stream to the client.</p></li> <li><p>If you are showing it a WEB application, and shows data on the web page where the rendered content is sent to the client then you need <a href="http://office.microsoft.com/en-nz/sharepoint-server-help/introduction-to-excel-services-and-excel-web-access-HA010105476.aspx" rel="nofollow">Excel Services</a> on the server (I think this is part of the SharePoint family), or a third party AS.NET control that ready .XLS info and renders it into the page.</p></li> <li><p>If the application is a desktop application that shows excel data in stand alone app where the user logs into the server as a desktop user then you need to have Excel installed on the server. Or you need third party .net control (dependant on app technology WinForms, WFP/Silverlight etc) that can read the .XLS info and present it.</p></li> <li><p>If the application is running on a virtual desktop, say like Citrix, then it's the same as 3.</p></li> <li><p><strong>If all you're doing is reading the files via OLEDB and then working with the data outside of excel</strong> then you can install the <a href="http://www.microsoft.com/en-us/download/details.aspx?id=13255" rel="nofollow">Access Connectivity Engine</a> for free. This basically the components needed to read various Office data in a need 'service only' package (or driver if you prefer). I don't if allows random access at the cell level, but I know it does allow you to run OLEDB queries over the .XLS file. We use for loading .XLS files into databases.</p></li> </ol> <p>All of these come with different licensing restrictions and costs. And without any of your use cases, all I can suggest is that you consider that Excel is a chunky set of application components and to use them you need to understand exactly how your application and they will function/interact and also their limitations in any particular deployment scenario you envisage.</p> <p><strong>Edit: Further info: If you are running on a 64 server and are using a 32 bit application then the only way I could ACE to work was to install the ACE 2007 and not 2010 version</strong> </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload