Run-time error 445

[David Anderson]

An app (apparently Visual Basic) fails with
Run-time error '445'
Object doesn't support this action

in a message box.   I click OK (the only choice) and the app dies.

A winedbg breakpoint on MessageBoxA
does not trigger.    On one occasion I got a breakpoint to work
and a traceback and the traceback ended in MSVBVM60 .   But  by 
yesterday I don't seem
to be able to get it to stop in a useful breakpoint (meaning one that had
anything to do with the problem).  Break)nFirstChance is 0 as
if it's 1 there are sooo many stops and so little progress...

Anyone with a clue about this? I'd appreciate any hints.
Thanks.

[Mike Hearn]

I usually do a +msgbox,+ole,+olerelay trace to get a basic idea of what's
going on here, moving up to +relay if necessary. If it's Visual Basic
stuff most likely you can see what's going on by monitoring OLE Automation.

Good luck!

-mike

[Eric Pouech]

David Anderson wrote:
> An app (apparently Visual Basic) fails with
> Run-time error '445'
> Object doesn't support this action
>
> in a message box.   I click OK (the only choice) and the app dies.
>
> A winedbg breakpoint on MessageBoxA
> does not trigger.    On one occasion I got a breakpoint to work
> and a traceback and the traceback ended in MSVBVM60 .   But  by 
> yesterday I don't seem
> to be able to get it to stop in a useful breakpoint (meaning one that had
> anything to do with the problem).  Break)nFirstChance is 0 as
> if it's 1 there are sooo many stops and so little progress...
>
> Anyone with a clue about this? I'd appreciate any hints.
> Thanks.

does a breakpoint on MessageBoxW works better (or CreateWindowExW) ?
A+

[Mike McCormack]

David Anderson wrote:
> An app (apparently Visual Basic) fails with
> Run-time error '445'
> Object doesn't support this action

Please report your bug to bugs.winehq.org, not wine-devel.  You'll have 
better luck getting help if your application is available for download.

Mike