> This is of major concern in your application design:
>
> "When one computer (client) has its set of data (say 30 records) it
> generates a string grid to represent that data. That screen may just
> sit there for hours."
>
> We are not talking desktop computing here!! If you have datasets that
> "just sit there for hours" then they need to be in read-only,
> read-committed transactions, or your users are going to want your guts for
> garters. Notifications (along the lines of DML Caching) are ideal for
> alerting read-only transactions of the need to refresh the clients'
> datasets in response to external changes.

Or some kind of client-dataset-buffer-thingy.

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com