| At the moment this value can be either "optimistic"/"fast" which is the default or "pessimistic"/"slow". It influences the manner in which the Database Manager re-scans a table when it is informed that a change did occur. It is also dependent on the parameter set per database; 'UpdateTime' - if no value exists there, there will be no auto refresh of that table! In the slow pessimistic mode the current selection is executed again, which means all displayed lines are read again. If you have a lot of computers working with the same table this can create a lot of network traffic and can use the server to capacity. In this case the fast optimistic mode is better, because only new and changed lines are read. There are two problems with the fast mode. First, if lines are deleted (really, not soft) and other lines are changed at the same time the deleted lines will remain in the view. If someone clicks on them a message box will appear, that they have been deleted recently. If this is not suitable to you, use the slow mode. The second problem is, that the local time of the workstations must be synchronized. If the difference is bigger than 1 minute the update will not work correctly. Note: if the "SortMode" of an ODBC data source is "External" the lines are always read completely. |