Steve Sinclair wrote:

> Of course if the form is shown modally this is fine or if the form had
> it's own transaction again no problem but of course if two forms have
> queries sharing the same transaction then it's always going to put all
> the open queries into the search state. I changed it to do a
> commitretaining instead of a hard commit and it's working fine now.
>
> I had to think a bit about what how much user intervention to permit
> over the transaction. I figured I could do one of the following:
> 1) Just use autocommit
> 2) Force the user to commit or rollback before loading a new form
> 3) Use a timmer to complain every so often to the user that he can't
> just leave transactions open.
> 4) Use a different transaction for each form
> 5) Just commitretaining if he loads a new form
>
> I suppose you've had endless conversations about this but using commit
> retaining seems to work for me for what I want this app to do :) I
> thought i'd note it all down in case it helps someone else in the
> future.

Hmmm, very clear! And an eyeopener for me! I think I start understanding
the transactionmodel.... to be sure: when using Commitretaining upon
closing an MDI-form, is it necessary to do a Commit when the application
exits?

Kind regards,
John