Office 2004 SP1 - What did it Fix??

W

Willis Eschenbach

Man, that is the most pathetic list of bug fixes I've seen in a while, and
at 22 megs, that's about 2 megs per fix! Meanwhile, Excel crashes at odd
times with nary a clue why, I send in my regular reports to Microsloth, and
what happens? Whoopee, they fix some obscure bug in the German version!

For those of us out here in the mid Pacific, paying premium rates for very
slow internet service, this is an expensive and insulting 22 megabyte bad
joke.

w.
 
J

JE McGimpsey

Willis Eschenbach said:
Man, that is the most pathetic list of bug fixes I've seen in a while, and
at 22 megs, that's about 2 megs per fix! Meanwhile, Excel crashes at odd
times with nary a clue why, I send in my regular reports to Microsloth, and
what happens? Whoopee, they fix some obscure bug in the German version!

For those of us out here in the mid Pacific, paying premium rates for very
slow internet service, this is an expensive and insulting 22 megabyte bad
joke.
Click to expand...

Like I said, it fixed more than what's on the list - for instance, in
XL, the Range.Copy bug in VBA appears to be fixed, along with some focus
problems associated with Userforms (Note: I haven't thoroughly tested).
Neither of these were on the list, but they correct things that were
show-stoppers for some of my clients.

I suspect that the list reflects MS's typical generalization when
releasing SP's: They often don't address particular bugs, apparently
under the theory that admitting the bug in the first place might lead to
liability. That's just my personal guess, tho'.
 
F

Frank

JE McGimpsey said:
Note that it fixes more than the KB says. I'm reworking some of the bugs
I list on my site.
Click to expand...

I've found that, with Excel, I now get a message on quitting "Compile
error in hidden module: AutoExec". This didn't occur before SP1. Is
this a bug?
 
P

Phillip M. Jones, CE.T.

JE said:
Like I said, it fixed more than what's on the list - for instance, in
XL, the Range.Copy bug in VBA appears to be fixed, along with some focus
problems associated with Userforms (Note: I haven't thoroughly tested).
Neither of these were on the list, but they correct things that were
show-stoppers for some of my clients.

I suspect that the list reflects MS's typical generalization when
releasing SP's: They often don't address particular bugs, apparently
under the theory that admitting the bug in the first place might lead to
liability. That's just my personal guess, tho'.
Click to expand...

On Cnet.news and Coumperworld they were characterized as critical
security update.

--
---------------------------------------------------------------------------
Phillip M. Jones, CET |MEMBER:VPEA (LIFE) ETA-I, NESDA,ISCET, Sterling
616 Liberty Street |Who's Who. PHONE:276-632-5045, FAX:276-632-0868
Martinsville Va 24112-1809 |[email protected], ICQ11269732, AIM pjonescet
---------------------------------------------------------------------------

If it's "fixed", don't "break it"!

mailto:p[email protected]

<http://www.kimbanet.com/~pjones/default.htm>
<http://home.kimbanet.com/~pjones/birthday/index.htm>
<http://vpea.exis.net>
 
P

Phillip M. Jones, CE.T.

Frank said:
I've found that, with Excel, I now get a message on quitting "Compile
error in hidden module: AutoExec". This didn't occur before SP1. Is
this a bug?
Click to expand...

On Acrobat newsgroup this is found to be caused by the PDFMaker.xla
file. (the file that creates that &*$# PDFMaker Thingi on word,excel,
and powerpoint menus.

create a folder named PDFMaker.xla and replace the file of the same name
with this folder. The Dratted PDFMaker will be gone forever and a day
(Unles you remove and resinstall Office).

Repeat for equivelent files in Word and Powerpoint as well.

--
---------------------------------------------------------------------------
Phillip M. Jones, CET |MEMBER:VPEA (LIFE) ETA-I, NESDA,ISCET, Sterling
616 Liberty Street |Who's Who. PHONE:276-632-5045, FAX:276-632-0868
Martinsville Va 24112-1809 |[email protected], ICQ11269732, AIM pjonescet
---------------------------------------------------------------------------

If it's "fixed", don't "break it"!

mailto:p[email protected]

<http://www.kimbanet.com/~pjones/default.htm>
<http://home.kimbanet.com/~pjones/birthday/index.htm>
<http://vpea.exis.net>
 
W

Willis Eschenbach

Like I said, it fixed more than what's on the list - for instance, in
XL, the Range.Copy bug in VBA appears to be fixed, along with some focus
problems associated with Userforms (Note: I haven't thoroughly tested).
Neither of these were on the list, but they correct things that were
show-stoppers for some of my clients.

I suspect that the list reflects MS's typical generalization when
releasing SP's: They often don't address particular bugs, apparently
under the theory that admitting the bug in the first place might lead to
liability. That's just my personal guess, tho'.
Click to expand...

Ooogh. I was afraid of that. Well, guess I've just got to bite the bullet
and pay the monkey for the connect time ...

Thanks, JE.

w.
 
B

Beth Rosengard

I've found that, with Excel, I now get a message on quitting "Compile
error in hidden module: AutoExec". This didn't occur before SP1. Is
this a bug?
Click to expand...

Hi Frank,

Another user reported that this error was due to the presence of the
PDFMaker add-in in the Excel Startup folder. Below is the procedure to get
rid of it based on a workaround by J.E. McGimpsey. I would appreciate it
very much if you would report back on whether or not this procedure works
for you.

--
***Please always reply to the newsgroup!***

Beth Rosengard
Mac MVP

Mac Word FAQ: <http://word.mvps.org/MacWordNew/index.htm>
 
C

Christoph Wild

Hi,

I had the same problem. Removing the PDFMaker add-in solved the the problem
for me.

cheers,

chris
 
M

M-Rick

Willis said:
Man, that is the most pathetic list of bug fixes I've seen in a while, and
at 22 megs, that's about 2 megs per fix! Meanwhile, Excel crashes at odd
times with nary a clue why, I send in my regular reports to Microsloth, and
what happens? Whoopee, they fix some obscure bug in the German version!

For those of us out here in the mid Pacific, paying premium rates for very
slow internet service, this is an expensive and insulting 22 megabyte bad
joke.

w.
Click to expand...
And still doesn't provide right to left support ... For a software at
this price how long we will have to wait to get something to work ?

Microsoft is very pathetic ....

Hope OpenOffice will be completed soon ...
 
H

Hugh

I've found that, with Excel, I now get a message on quitting "Compile
error in hidden module: AutoExec". This didn't occur before SP1. Is
this a bug?
Click to expand...

Thanks for the post. At least now I know I'm not crazy. I'm getting
the same message. I have no idea what it means. So far it doesn't seem
to affect the way the program runs, except that I can no longer shut
down and walk away. Assuming that someone from Microsoft is reading
these, will there be a fix of the fix, or is there some way to delete
the module in which there is a compile error?
 
T

The Terminator

Yes it does work...but what if we want the PDFMaker toolbar? Did SP1 ³break²
it until Adobe fixes it?
 
B

Beth Rosengard

From what I understand you don¹t need it. All it does is duplicate
functions/commands already inherent in Word/OS X. However if you really
want it, keep it; but I guess you¹ll have to put up with the error message.

I have already reported this to MS and if I hear anything, I¹ll post back on
this thread.

--
***Please always reply to the newsgroup!***

Beth Rosengard
Mac MVP

Mac Word FAQ: <http://word.mvps.org/MacWordNew/index.htm>
Entourage Help Page: <http://www.entourage.mvps.org>
 
T

The Terminator

So which component is broken ­ Excel or PDFMaker? The error is not happening
in Word or PowerPoint.
 
B

Beth Rosengard

The first person I responded to on this subject said it happened to him in
both Excel and Word (see ³PDFMaker Template - Opinions?² thread). I really
don¹t know where the fix needs to be made. It wouldn¹t be Excel. It could
have something to do with the Office SP 1 installation. Or it could be an
Adobe problem. Sorry ­ no answers at this point in time.

--
***Please always reply to the newsgroup!***

Beth Rosengard
Mac MVP

Mac Word FAQ: <http://word.mvps.org/MacWordNew/index.htm>
Entourage Help Page: <http://www.entourage.mvps.org>
 
M

matt neuburg

JE McGimpsey said:
Note that it fixes more than the KB says. I'm reworking some of the bugs
I list on my site.
Click to expand...

It sure didn't fix some of the main bugs I know about.

For example, if you set the filter in the Revisions toolbar to show only
Comments, and there are no comments, then if you press the Next button
in the toolbar, Word will crash. I've performed this crash reliably
dozens of times, and every time a report has presumably gone to
Microsoft. It isn't fixed.

There's a major bug in VBA in the Range.New method where you supply
numbers for the range's position: if your document has any fields in it,
the range may end up in completely the wrong place. This isn't fixed.

I could rattle on and on, but my point is, don't make the
reverse-psychology mistake of assuming that something is fixed merely
because it is *not* listed at that URL. m.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Microsoft Office Standard 2013 0
Descenders clipped 0
Office apps in chrome, toolbars are super tiny 0
"MSysCompactError", "System resource exceeded" & "You do not have the necessary permissions to use the...." 0
How to map SharePoint drives permanently 0
SP1 caused problems with opening Office files 5
Office 2008 Speed/Issues: Post SP1 2
sp1 installation 6

Top