Subject | Re: [IBO] Re: DMLCache and DMLCacheReceivedItem not fired |
---|---|
Author | Luiz |
Post date | 2003-01-31T16:30:50Z |
I am sure. You need differents users logged on database in order to
dmlcalching works to all them. You need also a tib_synccursor dropped in
your app.
I have an app using it.
Luiz.
dmlcalching works to all them. You need also a tib_synccursor dropped in
your app.
I have an app using it.
Luiz.
----- Original Message -----
From: <mmenaz@...>
To: <IBObjects@yahoogroups.com>
Sent: Friday, January 31, 2003 12:01 PM
Subject: [IBO] Re: DMLCache and DMLCacheReceivedItem not fired
> Are you sure? I think you are talking about DMLCache for notify about
> updates made by other uses. If you reqad the tech-sheet, you learn
> that it works for "internal" updates also (or, mainly).
> The tipical situation is that you update a table that is used in
> lookups queries.
> http://www.ibobjects.com/docs/ti_dmlcaching.ZIP
> "Explore this notification system which you can activate to keep all
> of the datasets synchronized throughout your application. Learn how to
> extend the scope of DML Caching to synchronize the datasets of all
> clients in your network so that, when one user executes DML, other
> users receive the updates."
> So, the basic use is "datasets synchronized *throughout your application*"
> regards
> Marco Menardi
>
> --- In IBObjects@yahoogroups.com, "Luiz" <cprmlao@i...> wrote:
> > Marco,
> >
> > DMLCache cache works only when there are users logged with differents
> > usernames in others connections to DB.
> >
> > You need, at least, another connection with an username other than
> the first
> > connection generating the event.
> >
> > So, these connections will be able to receive the event
> > OnDMLCacheReceiveItem.
> >
> > Luiz.
> > ----- Original Message -----
> > From: <mmenaz@l...>
> > To: <IBObjects@yahoogroups.com>
> > Sent: Thursday, January 30, 2003 9:04 PM
> > Subject: [IBO] DMLCache and DMLCacheReceivedItem not fired
> >
> >
> > > Hi, I've two datamodule, one with the connection and a transaction
> > > that is set as the default transaction of the connection, and another
> > > datamodule with a query against a table that I will use for editing
> > > (qryTableA), and a query that I use as a lookup (qryLk1), but uses
> > > another transaction local to this second datamodule. In addition, I've
> > > a query that is used in a form that has it's own transaction that is
> > > assigned to this query (qryCustomers_U_TableA).
> > > Well, I've all these 3 queries with all DMLCache set to true (for
> > > announce and receive), but when I edit a record in qryTableA the
> > > Announce event is generated, while the code I've put in the receive
> > > event of the other 3 queries is NOT.
> > > Is there some other property to set? I've also assigned explicit
> > > keylinks, but nothing happens :(
> > > Does DMLCaching work only for datasets under the same transaction? Do
> > > dataset need to belong to the same datamodule? Any idea?
> > > thanks a lot
> > > IBO 4.2Ib
> > > Marco Menardi