>>>What is the impact ( if there is one) in time responses on a transaction? Would any be delayed?
>>
>>Pablo,
>>
>>What time restrictions? Simply stated a transaction should last no longer than is absolutely required. This means do all the work first and when the only thing left to do is to TableUpdate start the transaction, do the updates and end the transaction.
>
>No Jim, I asked if a transaction punishes will increase the recording time, if there is any impact.

Pablo,

I still don't think I usderstand what you are asking. Are you asking if the time it takes to save the data is longer with a transaction than without one? The asnwer to that would have to be yes as the transaction si doing more than the simple TableUpdate. All of teh TableUpdates are done and then the data is committed. The committing of the data is the actual writing to disk. Both with and without transactions the TableUpdate and teh write to disk must occur, with teh transaction there is the one more step of logging the transaction actions so they can be committed together at once. So transactions must take longer. How much longer is probably not measurable.