Kevin,

What I believe this is supposed to address is having a native
(TIB_Dataset) dataset in dsInsert state while the query is merely in
a prepared state but not an active state.

It doesn't look to me like it was implemented properly for standard
behavior to be maintained on the TDataset compatibility.

I will have to spend some more time on this issue to figure out what
exactly my intentions were on it. I will go through my past changes
in code and see if I can find a time that it was altered and then
look at the release notes to see what was going on.

For now, simply change your code to have it work to your preference.

Thanks for raising my attention to this.

Jason Wharton

--- In IBObjects@yahoogroups.com, "kgdonn" <kgdonn@...> wrote:
>
> This procedure is implemented:
>
> procedure TIBOQueryDataLink.CheckBrowseMode;
> begin
> if Dataset.State <> dsInsert then
> if FIBDataset.Active then
> FIBDataset.CheckBrowseMode;
> end;
>
> I'm trying to understand the reason for not propagating on
dsInsert.
> This is not in line with TTable and breaks some of my code. You
can
> do a simple test project by doing the following:
>
> Put two TTables on a form with two TDataSources, two TDBNavigators,
> and two TDBGrids. Set up Table2 to have Datasource1 as a master.
> Run. Scroll DBNavigator1 to be off the first or last record.
Click
> DBNavigator1's insert and fill in some data. Click DBNavigator2's
> insert and fill in some data. Now without posting either of them,
> scroll DBNavigator1. The records in both Table1 and Table2 will
get
> posted.
>
> Now if you set up this same scenario using TIBOTables instead,
> Table1's record will get posted but Table2's won't due to the
> implementation of TIBOQueryDataLink.CheckBrowseMode.
>
> Am I missing something? Is it a bug? Would you like to provide a
> patch or should I just work around?
>
> Thanks,
> Kevin Donn
>