I am playing with some weird thing (at least for me). Two table components accessing the same disk table

Table1 opened
Table2 closed

Accessing DBSYS I change one record in the disk table

When I open the Table2 it uses the same buffer as Table1 and does not reflect the actual data in the table. The idea of opening a table shoud use the already used buffer in another table ? I understand the disk table should be read again. Of course if I call a Refresh before open Table2 it reloads the buffer according with disk table reflecting the changes.

Is it by design ? Or it could be a bug ?

Eduardo (HPro)

Jose Eduardo Helminsky wrote:

> When I open the Table2 it uses the same buffer as Table1 and does not
> reflect the actual data in the table. The idea of opening a table
> shoud use the already used buffer in another table ? I understand the
> disk table should be read again. Of course if I call a Refresh before
> open Table2 it reloads the buffer according with disk table
> reflecting the changes.
>
> Is it by design ? Or it could be a bug ?

Design, I think. There is an "Engine" underneath the tables which will
be doing the actual file access. The tables talk to this for optimal
use.

I think you might want to look at the options like
StrictChangeDetection (perhaps that is the wrong name) to be able to
pick up those changes quicker.

--

Matthew Jones