Subject | Re: [IBO] Re: DMLCache and DMLCacheReceivedItem not fired |
---|---|
Author | Jason Wharton |
Post date | 2003-02-01T02:59:30Z |
Can't remember how it is spelled but you just call the method where you want
the action to take place. This was a bit lazy for not having a flag as
handled and doing before and after handlers. One event and then being able
to invoke the default action was the simplest interface while still being
flexible.
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
-- We may not have it all together --
-- But together we have it all --
the action to take place. This was a bit lazy for not having a flag as
handled and doing before and after handlers. One event and then being able
to invoke the default action was the simplest interface while still being
flexible.
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
-- We may not have it all together --
-- But together we have it all --
----- Original Message -----
From: <mmenaz@...>
To: <IBObjects@yahoogroups.com>
Sent: Friday, January 31, 2003 3:41 PM
Subject: [IBO] Re: DMLCache and DMLCacheReceivedItem not fired
> Well, re-looking at my code, no, I was not committing (autocommit
> transaction)... but I have to investigate further, since in other
> situations DMLCache seems to work pretty well.
> Anyway, looking at the source I've seen that adding a
> OnDMLCacheAnnounce prevents IBO to perform standard DML change
> notification, while I thought that in the event handler you could ADD
> something to the notification. Removing the Announce event handler has
> made qryTableA change being notified to qryLk1. What I can't make work
> is having qryCustomers_U_TableA notified too. This is a many to many
> relation table, so it's keylink is qryTableA keylink plus qryCustomer
> keylink. So seems that IBO does notify that query in this situation...
> is it right? What can I do to avoid this?
> thanks
> Marco Menardi