How to know the active presentation's size? - excel

Is it possible to know the active presentation's size on the fly? I mean, we don't have to save as, and check on the file's size.
I tried to search for a similar property of the PowerPoint._Application.ActivePresentation, but cannot find out.
Any recommendation?
Thanks
Note: I am using PowerPoint 2013, C#, VS Ultimate 2013

No, you need to save the presentation first.

No. Because the format for storing the presentation in memory is different from the XML format used to export it to a file system object.

Related

Programatically pick PowerView properties from Microsoft Excel 2013 file

I have a requirement to programmatically read/handle PowerView properties like title, theme, background, font-size etc. from a Microsoft Excel 2013 file. Also I need to access the properties of the objects which are added on to the PowerView, for e.g. properties of a table or a image added to the PowerView.
I have been looking for it since long, but no luck. Is there a way by which I can achieve it? Any pointers regarding this would be really helpful.
Thanks in advance.
Power View properties are not exposed via the Excel object model.

Create docx with older msword8.h using Office 2010

When using Office Automation with MFC we have an old application written in Visual C++ that uses the headers from msword8.h of Word97, were are changing our systems to use Office 2010 i would like to know if without updating the msword8 files could i change the fileformat parameter while saving to save in .docx or do i need to update to new headers?
Sorry if i am not expressing myself right but i don't know a lot C++ and much less Windows programming. If any aclaration is needed be sure to ask.
Bonus question:
The way the SaveAs method is used is like: doc.SaveAs(filename, VT_BSTR)
I cant find where VT_BSTR was declared or how can i modify it, if some one could point me to the right direction it will be greatly appreciated.
If you are using office 97 you can't change file format. To save in word97 type you can use the following code.
COleVariant vOpt((long)DISP_E_PARAMNOTFOUND,VT_ERROR),vTrue((short)TRUE), vFalse((short)FALSE);
cstring filename;//send file path.
oDoc.SaveAs(filename,vOpt,vOpt,vOpt,vOpt,vOpt,vOpt,vOpt,vOpt,vOpt,vOpt,vOpt,vOpt,vOpt,vOpt,vOpt);
It's not possible to change VT_BSTR, is a pre defined enum which means: VT_BSTR [V][T][P][S]
OLE Automation string it's declared in wtypes.h.

Read excel file in Metro app (C#/XAML)

I want to find the way to read excel file in Metro app (use C#/XAML) but probably there is no solution. Anyone know if there is any reference support to do this (like Microsoft.Office.Interop.Excel in Win32)? Help me.
If you want it free, write your own ExcelReader, I've shared some idea here:
Reading Excel file using C# in WinRT platform
If you don't mind paying, you can try either ComponentOne or Syncfusion, they've got out of the box of manipulating (reading and writing) office documents.
There's paid control available from ComponentOne.

Exporting Native Excel 2007 Files From .NET

Does anyone know of resources that can help me export simple contents of a GridView to a native Excel 2007 format (i.e. the OpenOfficeXML format).
I've already seen solutions like Matt Berseth's, and in fact I have been using that for a while, but it comes with an annoying warning produced by Excel 2007 as documented here stemming from the fact that a native Excel file is not generated; rather it is HTML.
My initial research shows that, at the core, xlsx files are zip files, but I have no idea how to produce these or what goes in them.
Any suggestions (or tutorials) would be greatly appreciated.
CarlosAg has an ExcelXML writer which works really well. It isn't a native excel 2007 formatted file, but it will be readable in excel 2007.
You will need to write a little method to do the exporting manually, the API is very straight forward though. You will create a sheet object, then a row object, then a cell object. You can just loop through your data and output it. The examples on the site are pretty decent.
I prefer using Microsoft's own Open XML Format SDK. It is free, it is released by Microsoft and it creates real .xlsx files.
You can find the reference documentation here, as you can see, it is pretty straightforward to use.
SpreadsheetGear for .NET can read and write native xls and xlsx files and is easier to use (takes less of your time) than other solutions because it has an Excel like API so you don't have to learn anything about Open XML.
You can see some live ASP.NET (C# and VB) Excel Reporting examples here and download an evaluation version here.
Disclaimer: I own SpreadsheetGear LLC

How best to export native data to Excel without introducing dependency on Office?

Our product has the requirement of exporting its native format (essentially an XML file) to Excel for viewing/editing. However, what this entails is having a dependency on Excel (or Office) itself for our product build - something that we do not want.
What we have done is export the data from our native format to a csv file which can be opened in Excel. If user selects an option to open the generated report as well, we (try to) launch Excel application to open it (ofcourse it requires Excel to be already present on the client system).
The data for most part is flat list of records.
Is there a better format (or even a better way) to handle this requirement? This is a common requirement for many products - how do you handle this?
Excel versions, both 2007 and several previous, have native XML formats. 2007, obviously, is XML by default, and earlier versions have the ability to save as XML. This SO question deals with the issue. I'd guess a little inspection would give an idea of what's required. I don't know if a XSD/DTD exists for older versions, but a little creative Googling might yield something.
As other people pointed out, it is reasonably easy to generate Excel XML files. You can do this in multiple ways. For example:
By creating a template Excel XML document, and then using XML DOM to stuff your data into the template, or
Converting the template Excel XML into an XSLT, and then simply passing your proprietary XML as input to XSLT.
I'm using ExcelPackage to create spreadsheets in one of my side projects. Works pretty good, but (at least the version I'm using) its a bit limited when it comes to styling and calculations.
ExcelPackage lets you create OOXML docs (.xslx files) that are natively compat with 2k7, but you can download a plugin for previous versions of Office from MS.
We export our data either using Excel objects (COM based code) on client side or CSV file (usually on server side, but can be used on client side too). And we allow copy data from grids in simple html format, what can be pasted into Excel without problems.
For one customer we even had to export data [from sql stored procedure] into csv-like tab-separated format, but named file like xxxxx.xls - this way excel opened that file in more correct way than csv file. Ugly hack, but worked well.
CSV is most compatible format (no dependencies on external applications or libraries), but customers don't like it. Maybe we need to incorporate some XLS export code, this way all users will be happy :)
If .csv isn't formatted enough, you could create a template in Excel, and use a little bit of VBA code to import the CSV and format it appropriately. This way your app is only concerned with generating the .CSV, and will use the same .XLS for each export.
If you're careful, you should be able to get this to work with most versions of Excel seamlessly.
With Perl there are several modules that can be used to produce .xlsx files without requiring an Office installation. Among those :
https://metacpan.org/pod/Excel::Writer::XLSX is the most well-known, with support for many Excel features like colors, formatting, etc.
https://metacpan.org/pod/Excel::ValueWriter::XLSX (I'm actually the author) has less features but is optimized for fast writing of large amounts of data
If you are working in Java, Checkout the POI project from APACHE.
http://poi.apache.org/
Simple, nice, complete, powerful.
We started with Office on the server, but that's not very nice. We had to kill processes that hung, and had quite a bit of a performance dip. We thought about putting it on a different machine, but didn't bother after trying and using Aspose (commercial). We don't have a very large number of simultaneous users, but complex documents. Simple ones can be handled easier with csv.
I've used FlexCel Studio for a couple of projects now. It's very functional and fast. 100% managed code, no dependencies. Sounds like you'd use the "Reports" feature which allows you to define an empty report template in Excel, then pass datatable and volia, it's populated with your data.
TMS Software
We use a combination of OleDB and Interop. We found that Interop was much faster and used less memory, but it's a pain for compatibility issues, especially when using different language installs of Office.
OleDb has the advantage that you don't require Excel to be installed on the client machine. Both Interop and OleDb support multiple sheets (tables) per workbook which you cannot do with csv.
If you're using C# or VB.Net, and your data is in a a DataSet, DataTable or List<>, then you can use my free "Export to Excel" class.
It uses the free Microsoft OpenXML libraries (so you don't need to have Excel on your server), and lets you export your data into a "real" .xlsx file with just one line of code, eg:
DataSet ds = CreateSampleData();
CreateExcelFile.CreateExcelDocument(ds, "C:\\Sample.xlsx");
All source code is provided on the following page along with a demo project, completely free of charge (and popups !)
http://mikesknowledgebase.com/pages/CSharp/ExportToExcel.htm
Hope this helps !

Resources