Subject Re: [IBO] 3.6.Dd
Author Jason Wharton
Apparently it thought that the master record had changed somehow and so it
re-queryied the detail dataset.
At the worst there is a potential inefficiency here but I don't consider
this problematic behavior.

You have specified for your transaction to be read committed which means you
are willingly subjecting yourself to changes other users are making.

Jason Wharton
CPS - Mesa AZ

----- Original Message -----
From: "John Tomaselli" <jrt@...>
To: <>
Sent: Thursday, May 03, 2001 1:47 PM
Subject: RE: [IBO] 3.6.Dd

> Jason,
> I have a fairly major problem at one of my clients where the masterdataset
> is automatically resetting after the current user or others on the network
> makes changes to the records. For instance, I do a search on appointments
> where status = 1, 10 records are fetched to my grid. If I change the
> of 2 records from 1 to 2 and another user changes the status from 1 to 3
> 2 different records, I do not expect my grid to change unless I do a new
> search or sort. If the grid is left untouched for a few minutes it
> automatically updates and I now have 6 records in the grid.
> The following properties on set on the query.
> BufferSynchroFlags
> Before=rue
> After=true
> Insert=False
> Callbackinc = -1
> callbackInitInt=3000
> callbackRefreshInt=250
> all dmlcache flags = false
> no event alerts.
> Ib_Transaction =tiCommitted,autocommit=true
> Any Ideas?
> John
> Your use of Yahoo! Groups is subject to