I found a nice solution to my problem which is export Excel 2003 file from MVC3. I used this code and it works perfectly but only with Excel 2007 and Excel 2010. What I need is some solution that will make this code to work with Excel 2003 as well. I guess there is a way to do that, but I am still looking for the solution. In my project I already use this code in many places and I don't really feel like changing it at whole. I will be very thankful if someone could help me.
Excel first began to use the xml-type spreadsheet in 2007. To get it into an Excel 2003 format, you would have to recreate the xls 2003 binary file format, which would be very difficult without using the Excel library.
There is a utility that allows 2003 users to open an xlsx file:
http://office.microsoft.com/en-us/excel-help/open-an-office-excel-2007-workbook-in-an-earlier-version-of-excel-HA010014107.aspx
That might help you on the client side.
Related
I'm working on a Windows Application that has been around more than 20 years. It has a help file (.chm) that is built manually outside of the solution (i.e. not by Visual Studio or MSBuild) by compiling it in Microsoft HTML Help Workshop 1.4 from 1999. I would like to migrate this to the latest format such that it can be built as part of the release mode build process.
Is there a way to import the project (based on .hhp file) into a tool that builds the modern .mhsc-format help files? According to this Wikipedia article there was something called Microsoft Help 2 which was "the help engine used in Microsoft Visual Studio 2002/2003/2005/2008", which came after HTML Help Workshop and was succeeded by Microsoft Help Viewer, which was supported starting with Visual Studio 2010.
Preferably, there exits a way to migrate the .hhp/.chm project directly to Help Viewer, or maybe I have to download VS2010 and do it in two steps if indeed those two migrations are themselves supported. This stuff is so old it's hard to find relevant information on it. Thanks.
MS Help Viewer (.mshc) was difficult to manage at the time. It was made mainly for companies like Microsoft who code their help from a database.
You'll find some viewers and tools like MshcMigrate e.g. getting you from .CHM and .HxS -> .mshc.
There is no longer any need to purchase a mshcMigrate licence. The licence is free to use See also free key.
If you expect the users of your application to have internet access, another approach is to publish the help as HTML pages on a web server and link directly to those from your application.
Before migrating please note (for your existing workflow) the CHM Viewer is part of the Windows OS. A special viewer isn't required.
I can't find the SQL view in Access 2010 when I open the .mdb(access 97 format) database file created with Visual Basic 6 inbuilt database.
It works fine when I open a new database document ** (.accdb) ** in Access 2010, but that version of the access file (.accdb) is not supported in Visual Basics 6.0.
I know it's weird that I still use VB6 but I have no other go since my university only allows to use VB6.
So, is there any way I can solve this issue?
Thank you.
I am not sure what you mean by "can't find SQL view". You can open mdb files in Access 2010 and edit queries using both the query designer and also the SQL editor.
It is also possible to open accdb files using VB6. Here is the proper connection string:
Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\myFolder\myAccess2007file.accdb;
Persist Security Info=False;
Taken from:
http://www.connectionstrings.com/ace-oledb-12-0/standard-security/
We have a program that manually creates Excel files in BIFF8 format. This is a server program that runs on UNIX as well, so it doesn't use any COM library, but writes the file binary data itself.
It is used to work very well, but the files it generates can no longer be opened in Excel 2007 or 2010 when running in Windows 7 - Excel says the file is corrupted, but Open and Repair doesn't work as well, and the file is not opened.
When in Windows XP, the files can be opened in Excel 2007 with no problem.
Can you think of a reason for it not to work in Windows 7, or any possible workaround?
(We would like the program to be able to create files that can be opened by various Excel versions, and not to create separate BIFF8 and BIFF12 files)
I have found that OpenOffice/LibreOffice will often open Excel files that Excel itself won't. If you then save the file it may be possible to open it in Office 2007/2010. You can even automate this process, though that's a bit fiddly.
Is there anyway to use the Open Office SDK 2.0 to save a PowerPoint presention that you created using OOXML to a PowerPoint 2003 presentation? I know if you open a 2007 file and click Save As you have the option to save it as a PowerPoint 97 to 2003 document and I didn't know if I could do this grammatically using this SDK.
The reason I am asking this question is because I need to give the user the option to save data on a website in either Office 2007 or 2003 format. I much rather just use the same code to produce the document instead of having to have two code paths for PowerPoint 2003 and PowerPoint 2007.
Unfortunately, no. Open Office SDK 2.0 is built for and around System.IO.Packaging to work with the Open Document Format (the zip package that wraps up all the xml and other files for Office 2007, XPS, etc.) in processing the ECMA/ISO standard for Office 2007/2010 formats.
Is there a way to copy the class diagram generated by the LINQ To SQL ORM in VS2008 without using print screen (yes, I know it's pathetic)?
For example, when I create database projects in Visual Studio I can copy the database diagrams and save them later in Paint.NET in any image format. Any idea or suggestion will be greatly appreciated.
Print as PDF works for me using Acrobat.
I don't think it's possible.
Cropper is a great alternative for PrintScreen
I don't think you can do this through Visual Studio. However a quick web search revealed the existence of a produce called Entity Developer Express that appears to provide this facility. It's free too.