SE transaction log

With SE version 4.10 I've found that the transaction log can grow quite large after a single relatively simple transacation. For instance, deleting a single record's appearance in 2 tables and then updating a single field in the remaining records (worst case, only 399 of them) to adjust the value of a field showing the record's position in the table adds a megabyte to the transaction log. Adding the record back also adds a megabyte. 1. This seems rather high to me. What do you think? 2. If I don't plan on using the ROLLFORWARD DATABASE command is it OK to clear the the transaction log after every transaction? 3. Is the structure of the audit trail file different from the transaction log? 4 Is the only difference between the 2 logs that the transaction log file is used to track the entire database while the audit trail file is used for single tables? --- Peter Levine | peterl@minerva PBX Software Engineering | peterl@pnna Siemens ROLM Communications Incorporated | peterl@robadome.com