dennis wrote:

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

I guess Helen meant to restore to a new database (not overwriting
your old one).

>
>
> 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?
>

Not doing commit (only CommitRetaining) will get you into trouble, eventually.
CommitRetaining is fine, but not always. You will have to find some
points in your applications where you do a commit, and maybe just
refresh your screen by closing/opening queries.

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

Maybe the level of activity, usage pattern, hardware resources kept
problems out of sight.


--
Aage J.