If you haven't done so already, try implementing a standard pointy-clicky
studio version of the event on a data object to make sure that the
constraint violation is actually causing an event to be tripped off.
Also, what is the reason for making the project object be the listener for
all the data objects?
Another option could be the GF (Grace Frederick) superclass approach,
perhaps with a new twist (something I just began to play with) of using an
anonymous inner class to be the listener.
== Curt Springer, Team ND
At 04:44 PM 4/20/99 -0800, [EMAIL PROTECTED] wrote:
>In the after init event for the project, I'm adding the project as
listener to each
> of it's data objects (the project implements ISpDataObjectListener and
log messages
> confirm that the code which adds the listener is being reached). However,
when a
> database error occurs (a constraint violation, in this case), the
'onDatabaseErrorEvent()'
> method implemented by the project isn't being notified.
>
>Any idea(s) why?
>_________________________________________________________________________
>
>For help in using, subscribing, and unsubscribing to the discussion
>forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
>
>For dire need help, email: [EMAIL PROTECTED]
>
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
