Subject | [IBO] Re: IBO's use of StringList |
---|---|
Author | Eric Handbury |
Post date | 2002-09-16T00:40:35Z |
--- In IBObjects@y..., Helen Borrie <helebor@t...> wrote:
both the grid and the data_fields (or a subset), so having a small
query to populate the grid, and a larger query to display/edit the
fields would be non-optimal. I also think this strategy causes
synchronization problems between the 2 queries, because the states of
the 2 queries would have to mirror each other. For example, I use
ColorSchemes so if the user deletes a row, I would manually have to
ensure that both datasets are dssDelete in order for the proper red
colour to be displayed in both the grid and data fields. But I do see
some places where this strategy could have some benefits. Thanks.
Eric.
>single or
> A better client/server approach is to populate the grids with a
> small dataset as a "selector" and, in the same transaction, toperform
> another query to fetch back the single row for editing...this modelis
> commonly termed "drill-down" and IBO is highly oriented to it.I can't do this (for most queries). Most of my tabsheets contain
both the grid and the data_fields (or a subset), so having a small
query to populate the grid, and a larger query to display/edit the
fields would be non-optimal. I also think this strategy causes
synchronization problems between the 2 queries, because the states of
the 2 queries would have to mirror each other. For example, I use
ColorSchemes so if the user deletes a row, I would manually have to
ensure that both datasets are dssDelete in order for the proper red
colour to be displayed in both the grid and data fields. But I do see
some places where this strategy could have some benefits. Thanks.
Eric.