Master/detail synchronization when master is in Edit mode

[alex]

Hi I have this problem.
I have a TIBDataSet called "qMaster" and another one called
"qDetail".

qDetail is connected with qMaster in a master/detail config using a TDataSource. No problem in browsing.

But when I put in edit mode the master and I modify one of the master/detail indexes, the slave does not synchronize; looking at the slave parameters, it continues to have the old values.

How can I force the slave to "refresh" its parameters, without having to modify them directly?

[Jeff Overcash (TeamB)]

Post by alex
Hi I have this problem.
I have a TIBDataSet called "qMaster" and another one called
"qDetail".
qDetail is connected with qMaster in a master/detail config using a TDataSource. No problem in browsing.
But when I put in edit mode the master and I modify one of the master/detail indexes, the slave does not synchronize; looking at the slave parameters, it continues to have the old values.
How can I force the slave to "refresh" its parameters, without having to modify them directly?

The way TDataset works for this is that the details are opened after a scroll
even of the master. You can always manually close and reopen the detail when
the master changes it's key value. This usually means though that you have tied
your keys to business logic. This is always a bad design. Your primary key
should never be something tied to business logic.

[alex]

Post by Jeff Overcash (TeamB)

Post by alex
Hi I have this problem.
I have a TIBDataSet called "qMaster" and another one called
"qDetail".
qDetail is connected with qMaster in a master/detail config using a TDataSource. No problem in browsing.
But when I put in edit mode the master and I modify one of the master/detail indexes, the slave does not synchronize; looking at the slave parameters, it continues to have the old values.
How can I force the slave to "refresh" its parameters, without having to modify them directly?

The way TDataset works for this is that the details are opened after a scroll
even of the master. You can always manually close and reopen the detail when
the master changes it's key value. This usually means though that you have tied
your keys to business logic. This is always a bad design. Your primary key
should never be something tied to business logic.

Actually I need to show different detail values everytime the user selects (while in edit mode) a different value in one of the fields. So I used this field as the master/detail bind.


Actually I use this system to select which details shows when I change

[Jeff Overcash (TeamB)]

Post by alex

Post by Jeff Overcash (TeamB)

Post by alex
Hi I have this problem.
I have a TIBDataSet called "qMaster" and another one called
"qDetail".
qDetail is connected with qMaster in a master/detail config using a TDataSource. No problem in browsing.
But when I put in edit mode the master and I modify one of the master/detail indexes, the slave does not synchronize; looking at the slave parameters, it continues to have the old values.
How can I force the slave to "refresh" its parameters, without having to modify them directly?

The way TDataset works for this is that the details are opened after a scroll
even of the master. You can always manually close and reopen the detail when
the master changes it's key value. This usually means though that you have tied
your keys to business logic. This is always a bad design. Your primary key
should never be something tied to business logic.

Actually I need to show different detail values everytime the user selects (while in edit mode) a different value in one of the fields. So I used this field as the master/detail bind.
Actually I use this system to select which details shows when I change

Then one way to do this is to add an OnChange event of the TDatasource. When
you see that particular field change then close and open the detail.