Save as Web Page

[cwhaley]

I'm interested in hearing from anyone who has used "Save as Web Page"
on a regular basis. When I discovered it and how to use it about a year
ago, I was really excited about the time savings potential.

I publish an investment site at http://TSX.ProfiTrend.com, where I do a
weekly analysis and publish a series of data tables and charts, along
with my commentary. Formerly, I was converting all data tables and
charts to .jpg files, then adding my own navigation in HTML. I chose
..jpg's because the format stays constant and they were easier to
produce than HTML tables.

Anyway, Excel's Save as Web Page changed all that... sort of.

With the selection of this feature I can publish a whole workbook that
contains all tables and charts... instantly available for uploading to
my site. There's even a tabbed navigation bar added automatically.

The problem is that I get inconsistent results from browser to browser
when viewing the online version of the wokbook. It seems that I get
consistently great results with Safari, formatting distortions in IE,
and Firefox either displays everything as well as Safari, or won't
display anything (actually it displays a code dump). I thought that
XML, which is what Excel generates automatically was supposed to solve
these kinds of problems.

BTW, I started doing this from the Office X version of Excel, but the
problem persists with Office 2004.

And, yes, I've informed Microsoft; but as usual, no response.

OK, that's a long intro, and, no doubt, we're talking about a bug that
MS will have to fix; but I'd just like to know if anyone (more familiar
with the code Excel generates) has found a workaround.

 

[Bob Greenblatt]

I'm sorry that I do not have an answer for you, but feel obligated to
comment on 2 of your issues:

And, yes, I've informed Microsoft; but as usual, no response.

Microsoft monitors these forums and does indeed "listen" to the Send
Feedback from the help menu of its applications. They rarely answer any
query and I think it is unreasonable to expect them to. The responses are
accumulated and are heavily analyzed to determine what changes/fixes/etc.
Are to be made for the next product update or release.

OK, that's a long intro, and, no doubt, we're talking about a bug that
MS will have to fix;

As above, I think it is unreasonable for you to assign priorities to
Microsoft's development efforts. Although you find this problem to be a
serious shortcoming, there is no guarantee that any bug will ever be fixed.
In particular, you point out that you get consistently great results with
Safari. Why do think Microsoft ought to also insure great results with IE, a
browser it no longer supports, or Firefox, a browser that it has nothing to
do with?