--- Mark Hammond <[EMAIL PROTECTED]> wrote:
> Oops - that last mail snuck away from me!
>
> Enabling "debug mode" for event handlers is tricky -
> you probably
> could open the makepy generated file and locate the
> function in the events
> class:
>
> def _query_interface_(self, iid):
>
--- Mark Hammond <[EMAIL PROTECTED]> wrote:
> In that case, it may be that ADO is expecting your
> events to always handle
> certain methods - ie, when ADO itself tries to find
> an event handler you
> have not implemented, it will see the
> DISP_E_MEMBER_NOT_FOUND error (raised
> by Python, as th
Oops - that last mail snuck away from me!
Enabling "debug mode" for event handlers is tricky - you probably
could open the makepy generated file and locate the function in the events
class:
def _query_interface_(self, iid):
import win32com.server.util
if ii
> include DispatchWithEvents both the Execute() and
> Close() methods no longer work for my Dispatch object,
> with a "Member not found" error appearing. Why does
> Execute and Close work with Dispatch by itself but not
> when DispatchWithEvents is added?
>
> What I find interesting is that both th
I'm having difficulty understanding exactly how
DispatchWithEvents operates. I need to execute SQL
statements on tables in an Oracle database (using ADO)
and it runs fine when using Dispatch. However when I
include DispatchWithEvents both the Execute() and
Close() methods no longer work for my Disp
