Raith, Daniel wrote:

>The program doesn't keep transactions open. For the data that was lost,
>we use non-data aware, data entry screens that pass the data to a query
>manager that creates the transaction, inserts data, commits the
>transaction. There is another non-auto created form where the user
>creates little memos with a data aware screen which uses:
>TSQLConnection->TSQLDataSet->TDataSetProvider->TClientDataset, and when
>closed calls TClientDataSet.ApplyUpdates.
>
>I suppose though since the transaction is handled by the TSQLConnection
>component, which the main form creates, I should add a safety check on
>close of the main form to verify InTransaction. What is the default
>behavior if there was an active transaction and the TSQLConnection
>component was destroyed...I'll have to look into that.
>
>

Daniel,

Probably it will be rolled back. That is the point I raised, may be for
some cause (expcetion), the transaction was not commited, so the further
commands reside inside that uncommited transaction and at the end, the
component suite rolls it back.

see you !

--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br