Subject | Re: [IBO] IBO and QuickReport |
---|---|
Author | Nando Dessena |
Post date | 2001-08-23T07:15:55Z |
L'Attila,
ClientDataSets for that) and print from there, or you could have your
TIB_Query and TIBOQuery act in the context of the same repeatable-read
transaction, but that would have at least two major drawbacks: it
wouldn't account for deleted or inserted rows, and it would force you to
keep a transaction open for a potentially long time (with all the
consequences this would have).
Finally, you could use a regular TDBGrid to show the results of a
regular TIBOQuery and print them, avoinding TIB_Query altogether.
The first two solutions will force you to a double download (or at least
storage in memory) of the data, whereas the third is cheaper but less
flexible I think.
HTH
--
____
_/\/ando
> Ok, I'll use TIBOQuery, it works fine. But it's very important, that ayou could cache the results in some sort of memory table (I tend to use
> result, that I'll display in TIB_Grid with TIB_Query, exactly same as a
> TIBOQuery-result on QuickReport. Our database will update often. When user
> prints the report, he wants to see exactly same as in grid, but it may be,
> that it's 5-10 minutes after displaying grid. Can I transport
> TIBOQuery-result to TIBQuery?
> Or I have to print row-by-row from grid manually?
ClientDataSets for that) and print from there, or you could have your
TIB_Query and TIBOQuery act in the context of the same repeatable-read
transaction, but that would have at least two major drawbacks: it
wouldn't account for deleted or inserted rows, and it would force you to
keep a transaction open for a potentially long time (with all the
consequences this would have).
Finally, you could use a regular TDBGrid to show the results of a
regular TIBOQuery and print them, avoinding TIB_Query altogether.
The first two solutions will force you to a double download (or at least
storage in memory) of the data, whereas the third is cheaper but less
flexible I think.
HTH
--
____
_/\/ando