Hello Helen



Unfortunately I don't have so good technical knowledge about the sql engine.



Could you please describe what gstat returns? What measurement have each one
number bellow? (bytes, packet)

>Database
>"c:\fd\customers\pos-veneti\works\071215_egnatia_lags_on_ekdosi_arithmou\ne

w

>_ble_eg_pos-before-backup.fdb"
>
>Database header page information:
>
> Flags 0
> Checksum 12345
> Generation 4914769
> Page size 1024
> ODS version 11.0
> Oldest transaction 4897071
> Oldest active 4914740
> Oldest snapshot 4914740
> Next transaction 4914765
> Bumped transaction 1
> Sequence number 0
> Next attachment ID 0
> Implementation ID 16
> Shadow count 0
> Page buffers 0
> Next header page 0
> Database dialect 3
> Creation date Nov 16, 2007 13:28:27
> Attributes force write
>
> Variable header data:
> *END*
>

Is "safe restore" you mentioned something special that the classic database
restore? Does it have any extra setting?



In the application I use only the CommitRetaining. I do CommitRetaining
after each post and I do CommitRetaining instead of Commit in order remain
the dataset opened after each post. I do not start and commit the
transaction because after each one post I do a commit. This application runs
on pos machines 3 years now, I haven't face problems in transaction layer
with this mechanism. I do not say that is the most right way but is a
mechanism that covers what we want from the application, the direct update
of the database. Is something wrong with that with this way?



The most strange thing is that in other branches, the same application has
not problem at all. But I am still investigating



Best regards

Dennis







[Non-text portions of this message have been removed]