How to reproduce...
Run SQL 2012 SP2
Create a blank report in SQL 2012 Reporting Services (SSRS 2012)
Add a text box with some text
Save and Run the report
Export to DOCX format
Save file to a local directory
Open the directory in Windows Explorer and search for any text
List item
Opening the file in Word 2013 launches Word in [Compatibility Mode]. You can save the file over top of itself which shows a window stating "Your document will be upgraded to the newest file format". Completing this makes the document searchable but isn't really acceptable.
At first glance I am thinking SSRS is doing one of two things. It is saving as an older version of DOCX (maybe Word 2007). Or the file isn't quite right perhaps having a problem with the header/footer (pure speculation here).
So I need a solution that will either...
...fix the file and export it correctly so that we may search on it
...or be able to resave the Word files in with a batch program that resaves hundreds of DOCX files on a schedule.
A hotfix for this issue has been released on the office update
3039756 April 5, 2016, update for Office 2013 (KB3039756)
http://support.microsoft.com/kb/3039756/EN-US
Related
I want my results to open in an excel file when I run a query in Teradata Studio Express. Teradata Sql Assistant had this option, where you go and click on "export" option and whenever you run a query the resultset is always exported into an excel file. I am unable to see this option in Studio Express. Please note, my result set is populated in the Teradata Result Set Viewer, and I can export it from there but what I am looking for is to export it directly into an excel file, rather than viewing it here in teradata studio Express, when the query is run.
The SQL Editor view has an Export Results button located in the toolbar of the Editor. I tried to use it in 16.20.07 this evening to verify its behavior but encountered an internal error with a component of Studio Express. I can see that it is attempting to initiate a JDBC FastExport to route the results to the specified Excel file.
Perhaps you will have more success using this feature in Studio Express. Nevertheless, the feature is present.
I have Windows 7 64 bit. I installed vs 2010 on my machine from ISO file. I have not mount content to CD. I used one software that convert ISO image to CD/DVD media.VS 2010 was installed properly. With VS,sql also came. But when I trying to install sql 2008, from configuration tool-> sql server installation center, it is asking for file. When I am trying to browse that ISO file, that file is not visible in that browse dialog box. What can I do?
The installer needs to be able to see the setup.exe file and related folders in order to be able to work, it can't read the ISO file directly.
Either extract the contents of the ISO file to the filesystem or mount the ISO as a disc image and point the installer to there.
I have developed a website where when the user uploads a .doc or .docx file it will be converted to HTML and stored back to my root directory. The problem I am facing is my server in which my application is hosted does not support Office 2007 and they have Office 2003 components installed on the server.
Is it possible without using the Microsoft.Interop.Word.dll to directly read the .doc file, convert it to HTML and store in the root directory?
Yes, you can do it.
Take a look on CreateObject
Edited to add in reply to a comment
The point with CreateObject is that it will use the Word installed in the server, whatever the version installed. The only point is that you have to limit yourself to the lowest version available.
A file with the DOCX file extension is a Word Microsoft Office Open XML Format Document file.
The DOC format varies among Microsoft Office Word Formats. Word versions up to 97 used a different format from Microsoft Word version between 97 and 2003.
In Microsoft Office Word 2007 the binary file format was replaced as the default format by the Office Open XML format.
CreateObject can only use the version of the Word engine that is currently installed on the machine, so it may not be able to read the newer versions such as DOCX.
I'm working on a project that I'm trying to export data from textboxes in asp.net website project to a powerpoint file. I writing ofcourse in C#.
The whole concept is to use the data the a user inserts to the text boxes and they are sent after clicking a OK button directly to a powerpoint file. I'm using OFFICE 2007 so I'm using powerpoint 2007 for this.
A similar concept that I'm already using in the website project is doing the same thing but exporting to a WORD format file. I bumped against this following site a software to perform this and it's called: SoftArtisans. There website is http://www.softartisans.com/ .
Now, if somebody has a clue or a tutorial how I can do this, Export to a powerpoint file I'll be very thankful.
I am also using Microsoft SQL Server 2008 R2 to save the data in the database, so if maybe someone knows how to export the data from the textboxes from the website TO the database and then TO the powerpoint file that could help to.
Thank you very much for your help and support.
I would suggest using Office XML
HTH
I need a data store for single-user, read-only access. I need multiple tables, but not related. I also need to do two-column indexing. Seems like Jet is a good choice. Front end will be either VB or C#. The data is not user-entered data, but meta data about users and external files. What are the deployment issues for Jet -is it built into all Windows OS versions from xp onward? I plan on including the Access Database in the resource file.
MS Jet 4.0/DAO 3.6 are part of the operating system and are in Windows 2000, XP, Vista and Windows 7. They are updated by Windows Update and the security patches are applied as appropriate.
Alternatively to including the MDB file in the resource file you could build it if it isn't present. See the TempTables.MDB page at my website which illustrates how to use a temporary MDB in your app.
You can also use the Compare'Em utility
to keep the database files tables, fields, indexes and relationships updated as you upgrade your app.
See why-should-i-use-sqlite-over-a-jet-database, and try both.
The Microsoft Access .mdb driver is included with XP and up. It's part of MDAC.
There are a few other options for this, by the way. Look into SQL Compact, VistaDB, and SQLite.
Be aware that currently there are no 64 bit versions of the JET engine included with the operating systems!
The engines for 64 bit will be available with next Office. Beta can be downloaded from Microsoft Downloads
If you Google this you will see that Jet is no longer a standard part of Windows and has been deprecated. The ACE driver that is now part of Office 2010 does support MDB files, though Microsoft emphasizes that it is not a replacement for Jet. They want you to use SQL Express instead.
You can download and install the ACE driver separately, but note that for no sane reason you can not have the 32 and 64-bit versions of it installed on the same machine. If oyu have Office 2007 32-bit installed and you try and install the 64-bit ACE engine, it gives you this big dialog box that tells you you have to uninstall Office 2007 first.
We switched to sqlite. No more such hassles.
Be careful when using the CSV ODBC driver, there is a bug I discovered.
If you export an MS-Excel file to CSV format, you get double quoted text strings if the text string exported contains double quotes or commas embedded within it.
Example:
"Hello World", This is Eric.
exports as
"""Hello World"", This is Eric."
However, if you read in this data to an ODBC enabled program, then export the data back out, what happens is that the CSV ODBC Driver puts double quotes around text whether the text has embedded double quotes and/or commas, or not.
The huge problem with this is that you cannot run a FILE COMPARE on the original file exported from MS-Excel, and the newly created file (read in then output) from an ODBC enabled program using the CSV driver.
You will always get a FAILED FILE COMPARE (checksum) because the data is not equal. That really screws up QA/QC.
Also, another huge bug exists in ODBC Administrator
whereby you cannot edit the files the Text Driver recognizes/supports.
If you edit that entry, Chinese characters are stored in the Windows Registry. But it is a nice way to parse CSV data via ODBC instead of having to write your own code to strip out the extra Double Quotes.