ODBC - refreshing read-only cursorsΒΆ
Some ODBC database types do not automatically refresh a read-only cursor when the database is updated. This means that an update (delete, insert or write) may not be seen by a subsequent readu, nextu, prevu, findu or match[u] command, even in the same program. So far, this behaviour has been seen only with Oracle.
There are two ways to avoid this problem.
1 |
Put each set of updates between begin and commit function calls. |
2 |
Use the flush command on the affected file:
|
RELATED TOPICS |