Subject | How to prevent master from scrolling if detail dataset not in dssBrowse |
---|---|
Author | Christian Danner |
Post date | 2006-01-18T11:48:03Z |
Hello all,
what's the preferred way to prevent the master dataset from scrolling
while one of the detail datasets is in a state above dssBrowse.
Do I have to check the conditions within the BeforeScroll event of the
master dataset like
if detailQueries.State in [dssInactive, dssPrepared, dssBrowse]
then Abort;
And if so, is there an easy, general way to obtain a list of the
linked detail datasets to be checked, or do I have to scour the whole
application for them?
IMO it would even be better to 'in-/activate' the chain of all linked
master datasets (and possibly their controls) within the
OnStateChanged (resp. AfterInsert, ~Edit, ~Delete / ~Cancel, ~Post)
events of the detail datasets (or within AfterStart / ~End of the
underlying explicit transaction). Does IBO offer a solution to achieve
this behaviour in a simple and general manner?
Sorry, a lot of questions, but a lot of options too.
Thanks
Christian
what's the preferred way to prevent the master dataset from scrolling
while one of the detail datasets is in a state above dssBrowse.
Do I have to check the conditions within the BeforeScroll event of the
master dataset like
if detailQueries.State in [dssInactive, dssPrepared, dssBrowse]
then Abort;
And if so, is there an easy, general way to obtain a list of the
linked detail datasets to be checked, or do I have to scour the whole
application for them?
IMO it would even be better to 'in-/activate' the chain of all linked
master datasets (and possibly their controls) within the
OnStateChanged (resp. AfterInsert, ~Edit, ~Delete / ~Cancel, ~Post)
events of the detail datasets (or within AfterStart / ~End of the
underlying explicit transaction). Does IBO offer a solution to achieve
this behaviour in a simple and general manner?
Sorry, a lot of questions, but a lot of options too.
Thanks
Christian