Kbase P21912: Making a request to find a record not always gets the newest copy of the record
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/18/2010 |
|
Status: Unverified
SYMPTOM(s):
Making a request to find a record not always gets the newest copy of the record
Using a PROGRESS client (4GL, AppServer, web-agent)
Using FOR EACH, PRESELECT EACH, OPEN QUERY or FIND statements with the NO-LOCK option.
Modifications to a record do not appear to take effect until the session is quit and restarted.
FACT(s) (Environment):
Progress 8.x
Progress 9.x
OpenEdge 10.x
CAUSE:
If the record is already being used NO-LOCK by another 4GL buffer then the old copy usually remains in memory rather than replacing it with a new copy. For this reason you could not always retrieve the newest record.
FIX:
Use the -rereadnolock Parameter introduced in Progress 8.3B. The -rereadnolock startup parameter causes PROGRESS to discard the older record and replace it with the latest version.