Are data controls such as TDBEDit a bad idea when creating an application that will
connect to an ElevateDB server over an internet connection?

Or is it better to just use regular TEdit controls and load them them yourself from a
TEDBQuery or TEDBTable?

Just wondering.

Dale

Dale


Some people hate databound controls - I love them. The thing to avoid over the internet is "chattiness" which means using the fewest sql or table commands, sorting out in some way (possibly via joins in a query) any lookup fields which mean constant traffic.

With DBISAM and ElevateDB most (all) of the time only the data required to satisfy the visual components or processing is transferred so use databound contrtol if you like them.

Roy Lambert [Team Elevate]

<<Some people hate databound controls - I love them. The thing to avoid over the internet
is "chattiness" which means using the fewest sql or table commands, sorting out in some
way (possibly via joins in a query) any lookup fields which mean constant traffic.

With DBISAM and ElevateDB most (all) of the time only the data required to satisfy the
visual components or processing is transferred so use databound contrtol if you like them.>>


So using data controls, if the user scrolls through a query or table, will the server have
to process each record as the user scrolls?  Or will the table or query be cached on the
client side, and only be updated when the user scrolls beyond the limits of the cache?  

Dale

Dale

>So using data controls, if the user scrolls through a query or table, will the server have
>to process each record as the user scrolls? Or will the table or query be cached on the
>client side, and only be updated when the user scrolls beyond the limits of the cache?

From previous posts of Tim's I believe its the latter.

Roy Lambert [Team Elevate]

Roy,

<< From previous posts of Tim's I believe its the latter. >>

You are correct.  Furthermore, with EDB the remote cache is bi-directional
(DBISAM is unidirectional), so you can use Next..Prior..Next..Prior and
still have the cache be used for all of the operations.  This is important
because the built-in TDBGrid (and any multi-row data-aware control in
Delphi) loads the internal TDataSet record buffers in just such a fashion.

--
Tim Young
Elevate Software
www.elevatesoft.com