I created a report for the Accounting department that exports the results to Excel (EXL2K FORMULA). When I tested the reports on a box running XP and Excel '07, I was warned that the file wasn't in the format specified by the file extension (.xls), but prompted me as to whether the source was trusted or not, to which I select "Yes", and the file is opened.
The accountants, running Windows 7 but the same version of Excel '07 recieve the same error but are not given the opportunity to verify the authenticity of the file. Even when saved to the disk and opened in notepad, the file is empty.

I figured I could fix the problem by exporting the results to EXL07, which opened in the XP version's Excel '07 without a single error. However, when the Windows 7 box was used, the same error as before was thrown, and the file was unable to be opened.

I had them download a compatibility package but that didn't help.

Has anyone experienced this problem and knows how to rectify it? The only difference between the two boxes seems to be the OS.

Thanks, Joe

This message has been edited. Last edited by: jjeanjaquet,

Well reported on the this forum and on Microsoft forums.

There is a registry fix.

It's Microsoft that's caused the problem.

Do a search.

I found a registry fix online but didn't really want to deal with that. As it turns out, we had licensing to upgrade them to Office 2010 so we took care of that yesterday.

The combination of Windows 7 and Excel '07 have been a problem for those downloading files from the internet according to Microsoft Forums.

The Windows 7 people still have issues downloading files in .xlsx, but the .xls files work fine now.

So what keywords do I use to search for this problem on Focalpoint?

I tried "Windows 7 Excel" and "Windows 7 registry" and I only get relavant hits to this thread.

I read the Focalpoint digest weekly and I didn't notice a thread discussing problems with Windows 7 and EXL2K Focus output format requiring a registry hack.

Can someone throw a bone to a clueless person on this problem. We seem to have it at our institution.

I wish Microsoft would stop changing their products to break the competition. The only ones who suffer are their customers.

-- Dan at UNO --

I'm not sure where in Focalpoint this is found. I looked for quite a while without success before posting on the Forum. I ended up finding a registry fix (which I didn't use) by doing a google search and found this.

http://www.itexperience.net/20...-the-file-extension/

You'll have to let me know if this works.

According to the same page it should help to change the mime-type for excel <= 2003 files to application/msexcel

I tried modifying WebFOCUS' mime.wfs and tomcat's web.xml file to use that mime-type, but it doesn't appear to have any effect - the report is still sent as application/vnd.ms-excel;charset=ISO-8859-1 (according to Firebug).

I did restart the WebFOCUS server and tomcat - what did I miss?

It turns out that the WebFOCUS client mime.wfs is the one to modify for this (I originally modified the server one), but alas, it doesn't seem to have any effect on the problem. Perhaps application/msexcel isn't the right mime-type either?

This message has been edited. Last edited by: Wep5622,