Kbase P21393: When do changes made to records appear in a browse?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
17/03/2003 |
|
Status: Unverified
GOAL:
When do changes made to records appear in a browse
FIX:
The browse feature that affects when a record is re-read from the database is the record cache. (Record cache can be set on any query by using the "CACHE n" option in the DEFINE QUERY statement.)
Record cache casues a certain number of records to stay in the client memory so that when you go to a previous screen then back to the current one, you don't have to re-read the records every time. (This enhances browse performance.)
By default, a single-table browse has a cache of 50 records. A multi-table browse (where the underlying query is a join) has a default cache of 30 records. While browsing within the range of cached records, you won't see changes that someone else might have made to the database since you opened your query, although you will be able to see changes that you yourself have made.
Reposition to recid clears a client's record cache, and thus causes database records to be re-read. You will then be able to see all record changes to the database that have been made by all users.