http://bugs.winehq.org/show_bug.cgi?id=11415
Summary: Word 2000 VBA editor and macros errors Product: Wine Version: 0.9.54. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: raydar@inetnebr.com
Created an attachment (id=10545) --> (http://bugs.winehq.org/attachment.cgi?id=10545) alert resulting from Tools-->Macro-->Macros-->VBA Editor
In Word 2000,
Tools-->Macro-->Visual Basic Editor causes a "Could not open macro storage" alert to appear. Clicking OK on that alert causes the same alert to appear again. Clicking OK a second time gets the alert to stay gone and the VBA editor to open, but with no programming pane. Closing the VBA editor and then reopening it, without shutting down Word in between, reopens the VBA editor without any alert appearing.
Tools-->Macro-->Macros gives the expected macro box, but clicking "Create" results in a "The project item name is not valid" alert. Clicking the "Organizer" button does bring up the Organizer Box, but with no macros listed.
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #1 from Ray raydar@inetnebr.com 2008-01-31 08:22:55 --- Created an attachment (id=10546) --> (http://bugs.winehq.org/attachment.cgi?id=10546) alert resulting from Tools-->Macro-->Macros-->Create
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #2 from Ray raydar@inetnebr.com 2008-01-31 08:23:47 --- Created an attachment (id=10547) --> (http://bugs.winehq.org/attachment.cgi?id=10547) VBA editor after opening it and OK'ing 2 alert identical boxes
http://bugs.winehq.org/show_bug.cgi?id=11415
Ray raydar@inetnebr.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |raydar@inetnebr.com
http://bugs.winehq.org/show_bug.cgi?id=11415
Ron ronleach@tesco.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ronleach@tesco.net
--- Comment #3 from Ron ronleach@tesco.net 2008-06-09 13:06:50 --- May I confirm that I experience this? Using Debian Etch, with Wine 1.0rc2 (a Debian build here: http://people.debian.org/~ovek/wine/README ), Winword in Office 97 reports 'no macro storage', twice, then the VBA editor flashes onto screen briefly but disappears. [Using standard config (all builtin dlls), and set to Windows 98.]
This is my first report, apologies if this is not still an open issue, I cannot run a later Wine version to check it still occurs in rc3 and rc4, and I haven't found any other report of the issue.
As for severity, from the user point of view, most of our use depends on VBA extensions to Word and Excel. It's severe for us (preventing use), but not sure if that's what the severity rating is meant to record.
regards, Ron
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #4 from James Hawkins truiken@gmail.com 2008-06-09 15:03:43 --- *** Bug 13807 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #5 from dimesio@earthlink.net 2008-06-21 11:21:46 --- Created an attachment (id=14250) --> (http://bugs.winehq.org/attachment.cgi?id=14250) Console output from opening Word 2003 Visual Basic Editor
I can confirm that this bug also affects Word 2003, tested on 1.0, openSUSE 10.3. The error message from Word matches the screenshots that have already been uploaded. I'm attaching my console output from opening Word and selecting the Visual Basic Editor from the tools menu.
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #6 from dimesio@earthlink.net 2008-06-21 11:44:28 --- Created an attachment (id=14251) --> (http://bugs.winehq.org/attachment.cgi?id=14251) Console output trying to record a macro in Word 2003
Word 2003 also generates an error message when trying to record a macro. I'm putting it here because I believe it's the same bug (the console output is nearly identical). Let me know if I need to open a separate bug for it.
http://bugs.winehq.org/show_bug.cgi?id=11415
dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dimesio@earthlink.net
--- Comment #7 from dimesio@earthlink.net 2008-09-13 18:48:04 --- Still a problem in 1.1.4.
http://bugs.winehq.org/show_bug.cgi?id=11415
Joshua joshudson@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |joshudson@gmail.com
--- Comment #8 from Joshua joshudson@gmail.com 2008-10-16 21:30:33 --- I can confirm this bug is still present in 1.0b3. Since it is also confirmed in 1.1.4 it is almost certainly not fixed in 1.0
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #9 from Joshua joshudson@gmail.com 2008-10-16 22:52:55 --- Created an attachment (id=16693) --> (http://bugs.winehq.org/attachment.cgi?id=16693) trace of trying create macro in word 2003, pruned
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #10 from Joshua joshudson@gmail.com 2008-10-16 22:54:15 --- Created an attachment (id=16694) --> (http://bugs.winehq.org/attachment.cgi?id=16694) trace of trying create macro in word 2003, full (very large)
I'm really hoping that this doesn't get attached as an email to everybody here
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #11 from Joshua joshudson@gmail.com 2008-10-16 22:55:40 --- I did some analysis and it looks like some interop between the Word process and the VBA process simply isn't working. By the looks of things ConnectToNamedPipe is failing when it shouldn't be but I'm not quite so sure.
http://bugs.winehq.org/show_bug.cgi?id=11415
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #12 from Lei Zhang thestig@google.com 2008-10-21 17:37:10 --- confirming then
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #13 from Rosanne DiMesio dimesio@earthlink.net 2008-12-27 22:54:41 --- This also affects Word 2007. Still present in 1.1.11.
http://bugs.winehq.org/show_bug.cgi?id=11415
Michael Coupet compmastermike@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |compmastermike@yahoo.com
--- Comment #14 from Michael Coupet compmastermike@yahoo.com 2009-01-14 16:24:25 --- Using a native oleaut32.dll allows me to create and edit macros with no errors, so I'd assume this is an ole bug.
http://bugs.winehq.org/show_bug.cgi?id=11415
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |oleaut32
--- Comment #15 from Vitaliy Margolen vitaliy@kievinfo.com 2009-01-14 20:39:39 --- Changing component.
http://bugs.winehq.org/show_bug.cgi?id=11415
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bunglehead@gmail.com
--- Comment #16 from Nikolay Sivov bunglehead@gmail.com 2009-01-16 15:19:50 --- (In reply to comment #14)
Using a native oleaut32.dll allows me to create and edit macros with no errors, so I'd assume this is an ole bug.
If it's so +ole log needed.
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #17 from Joshua joshudson@gmail.com 2009-01-16 20:59:05 --- as for native oleaut32, what other DLLs are native and what versions of the dlls did you use, and what version of Word?
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #18 from Rosanne DiMesio dimesio@earthlink.net 2009-01-18 21:17:11 --- Using native oleaut32.dll copied from my XP partition does NOT solve the problem for me in Word 2003, Wine 1.1.13.
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #19 from Rosanne DiMesio dimesio@earthlink.net 2009-01-18 23:01:48 --- Simply creating an empty stdole2.tlb in Wine's system32 directory solves the problem for me in Word 2003, Wine 1.1.13, no overrides.
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #20 from Rosanne DiMesio dimesio@earthlink.net 2009-01-19 11:59:45 --- I tried an empty stdole2.tlb with Word 2007, and while it got me past the initial error message, macros still didn't work properly. Copying a real stdole2.tlb from XP and setting an override for oleaut32 (also from XP) allowed me to record, edit, and run macros so long as I kept the document open, but there were file save errors when closing the document, and errors in saving the normal template when closing Word. I think that's a separate bug--I'll open a bug report for that once I get the chance to do a little more testing.
I don't have Word 2000, so I can't test that version.
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #21 from Ron ronleach@tesco.net 2009-01-19 12:28:57 --- Neither recent suggestions worked for me running Office97, Wine 1.1.9 from Fedora repository, FedoraCore8 (Linpus), Acer AspireOne netbook.
Blank stdole2.tlb in system32 folder had no effect. (filename in lower case - does it matter?)
Real oleaut32.dll, from W98se, in system, and in system32 folders, had no effect. Noted that oleaut32.dll in Wine 1.1.9 is approx 5kB, whereas W98se version seems to be around 600kB.
Note - did not change 'overrides', assuming that placement of the files was sufficient. But was that correct to do? Happy to test again, if mistaken here.
Symptoms remain:
Word97, opening VBA editor - 'cannot open macro storage' (twice, then VBA editor flashes on and immediately closes.
Excel97, opening an xls containing a macro - 'Not enough memory' VBA error Excel97, opening VBA editor, VBA editor flashes on then immediately closes.
Powerpoint97, opening VBA editor - 'an error occurred which powerpoint cannot manage, please close all documents'.
These are the same symptoms I had when running an earlier release (1.0 rc2?)on Debian Etch.
regards, Ron
http://bugs.winehq.org/show_bug.cgi?id=11415
Jaime Rave jaimerave@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jaimerave@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #22 from Rosanne DiMesio dimesio@earthlink.net 2009-05-24 10:43:07 --- This was fixed for Word 2003 in 1.1.14, and is fixed for Word 2007 in 1.1.21 (may have been earlier; I haven't tested in awhile).
It is not fixed for Word 97; winetricks dcom98 is the workaround.
Can someone test this in Word 2000 in current Wine?
Note that this bug is for Word only; there is a separate bug (#15282) for Excel macros.
http://bugs.winehq.org/show_bug.cgi?id=11415
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #14250|0 |1 is obsolete| |
http://bugs.winehq.org/show_bug.cgi?id=11415
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #14251|0 |1 is obsolete| |
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #23 from Austin English austinenglish@gmail.com 2009-12-31 11:53:25 --- Ron/Ray, please retest.
http://bugs.winehq.org/show_bug.cgi?id=11415
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wylda@volny.cz
--- Comment #24 from Wylda wylda@volny.cz 2010-01-03 08:05:43 --- (In reply to comment #22)
This was fixed for Word 2003 in 1.1.14, and is fixed for Word 2007 in 1.1.21
Can someone test this in Word 2000 in current Wine?
(In reply to comment #23)
Ron/Ray, please retest.
I did the retest based on Commnet #0 under wine-1.1.35-364-g9dc584d and did not find any problem, i.e. FIXED also for Word2000.
http://bugs.winehq.org/show_bug.cgi?id=11415
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #25 from Dmitry Timoshkov dmitry@codeweavers.com 2010-01-03 08:15:18 --- Reported fixed.
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #26 from Rosanne DiMesio dimesio@earthlink.net 2010-01-04 10:13:55 --- (In reply to comment #25)
Reported fixed.
It's not fixed for Word 97. Native oleaut32.dll (copied from XP) is still needed. Should I open a separate bug for this?
http://bugs.winehq.org/show_bug.cgi?id=11415
--- Comment #27 from Austin English austinenglish@gmail.com 2010-01-04 12:10:57 --- (In reply to comment #26)
(In reply to comment #25)
Reported fixed.
It's not fixed for Word 97. Native oleaut32.dll (copied from XP) is still needed. Should I open a separate bug for this?
Please.
http://bugs.winehq.org/show_bug.cgi?id=11415
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #28 from Jeff Zaroyko jeffz@jeffz.name 2010-01-09 04:45:28 --- Closing bugs fixed in 1.1.36.