It looks to me like you also have a KeySource based relationship configured
somehow.

This could also be the result of fixing a bug some time ago that the detail
dataset's AfterScroll event was not firing when the master dataset was
scrolled...

Hmmm...

> TIB_Column.Clear
> TIB_Column.Assign(???)
> TIB_Dataset.SysUpdateKeyLinksData
> TIB_Dataset.SysAfterScroll
> TIB_BDataset.SysAfterScroll

This is the section I am curious about. Why would it call
SysUpdateKeyLinksData?

Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "Nando Dessena" <nandod@...>
To: <IBObjects@yahoogroups.com>
Sent: Wednesday, November 21, 2001 11:24 AM
Subject: Re: [IBO] Strange behaviour with linked IB_Grids


> Jason,
>
> > What would be helpful is if you could retrieve the callstack of it going
> > into edit mode.
>
> One of these days I should write a small expert to grab the text of the
> call stack window. Has anyone such a tool already available?
> Anyway, Here's more or less what I found by putting a breakpoint in the
> BeforeEdit event of the third query:
>
> <third query beforeedit handler>
> LanunchDSEvent(???, some address)
> TIB_Dataset.DoBeforeEdit (this is the detail-detail dataset).
> TIB_Dataset.SysBeforeEdit
> TIB_Dataset.SysEdit
> TIB_Dataset.SysBeforeFieldDataChange(???, ???)
> TIB_Row.DoBeforeModify(???)
> TIB_Row.SysBeforeModify(???)
> TIB_Row.SysBeforeColumnModify(???)
> TIB_Column.SysBeforeModify
> TIB_Column.SetIsNull(True) (did I say that if I try to post the edit it
> complains that the key field is not assigned?)
> TIB_Column.Clear
> TIB_Column.Assign(???)
> TIB_Dataset.SysUpdateKeyLinksData
> TIB_Dataset.SysAfterScroll
> TIB_BDataset.SysAfterScroll
> TIB_Dataset.SysRefresh(False)
> TIB_Dataset.RefreshKeys
> TIB_Dataset.SysAfterParamsDataChange(???, ???)
> TIB_Row.DoAfterModify(???)
> TIB_Row.SysApplyUpdates(???)
> TIB_Row.EndUpdate(???)
> TIB_Dataset.SysMasterDataChange(???)
> TIB_Dataset.IB_MasterDataChange(???, ???, nil)
> TIB_DataLink.DoDataChange(???)
> TIB_DataLink.SysDataChange(nil)
> TIB_DataLink.ProcessStatementEvent(setFieldsDataChange, 0)
> TIB_DataSource.ProcessEvent(setFieldsDataChange, 4299748)
> TIB_Statement.ProcessEvent((out of bound) -28, 4332764) (this just
> doesn't look good)
> TIB_Dataset.ProcessLinkEvent(setFieldDataChange, 0)
> TIB_Dataset.EnableControls
> TIB_Dataset.MoveBy(???)
> TIB_Dataset.Next
> <navigation bar calls>
>
> Hope this helps some.
> For the sake of completeness I'll add that I am doing a Refresh of a
> dataset that is used as a lookup by the third query, and I am doing it
> in the afteredit and afterinsert event of this third query.
> I am also calling RefreshRows on the second query in its own afterpost
> handler.
>
> Ciao
> --
> ____
> _/\/ando
>