At 11:18 PM 14/02/2003 +0000, you wrote:

>Hi there,
>
>I am building an application that will run over a WAN and would like
>to know if, in general terms, using TIBOQuery (for data entry
>screens) would be better than TIBOTable, i.e., which one is more
>suitable for a low-bandwidth scenario.

You definitely shouldn't use TIBOTable. Actually TIBOTable doesn't belong
in client/server apps at all, extra-especially not in the thin-client web
browser or WAN client scenario.

>Also, I believe that calling
>the 'Last' method is bringing over all the data from the server to
>the client and not only the true last record in some smart way. Am I
>correct?

Perfectly correct. Don't deliver desktop-style datasets across a
WAN. Make use of selector-type queries to load up into a persistent
container such as a non-data-aware combobox, and collect parameters from
these to query for one or a very small number of records.

You can use the native IB_Cursor for loading up your non-data-aware client
containers, e.g. at FormCreate, even though you are using the
TDataset-compatible controls for the GUI stuff. The same goes for
operations you want to do - you can use IB_Cursor or IB_DSQL for
those. Those components will hook up their IB_Connection and
IB_Transaction happily with your TIBODatabase and any extra
TIBOTransactions you want to piggyback onto TIBODatabase.

cheers,
Helen