[Bug 8795] Excel 2003 on AMD64: Visual Basic not working

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=8795





--- Comment #22 from max at veneto.com  2008-06-14 02:20:50 ---
(In reply to comment #21)
> (In reply to comment #20)
> > BTW, using DCOM98 does enable VBA usage, but inhibits the execution of more
> > instances of excel, giving the "IOPL not enabled" error when trying to execute
> > second instance.
> 
> "IOPL not enabled" is the bug 9422. Does installing gdiplus help to eliminate
> it?
> 

Nope.
The complete situation is this one :

1) With builtin ole (ole32, oleatu32, rpc4), there's NO iopl problem (even with
builtin gdiplus), but VBA doesn't work, as this bug reports.
You can indeed run as many instances of Excel as you like.

2) Installing DCOM98, which overrides ole32, oleaut32 and rpc4, VBA works
perfectly BUT you can run just one instance of Excel. Trying to start the
second one, brings IOPL error.

3) With ole32, oleaut32 and rpc4 taken from windows xp, vba doesn't work,
ole/activex doesn't work either and vba project embedded in excel is trashed.

Gdiplus doesn't help in this case... I think the vba problem is because of ole
and dcom98 ole, while resolving vba problem, brings again iopl one.

Ciao

Max


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.