>I have just deployed an small application on three PC which are all PIII 500 32MB. The apllication started to hand the PC after entering 15 to 20 records. I had not used transaction while saving to file. After introducing begin & end transaction in save and delete routine the problem was sorted out.
>
>Now the only place where the PC hangs is when the user wants to reverts after stating a add or edit procedure. Here as tablerevert function cannot be included in begin & end transaction I am clueless about which way to go to solve this problem.
>

Cancelling a transaction involves doing a ROLLBACK rather than END TRANSACTION to terminate the transaction. This is the transactional equivalent of TABLEREVERT(), except that it affects all changes to all tables involved in the transaction.

>Is begin & end transaction necessary while updating more than one table.
>

More than in the single table situation; transactions affect all data changes within the scope of the transaction. Either all affected records of all tables succeed, or everything reverts to the state before the start of the transaction. Transactions provide a way to ensure that all changes to all tables succeed, as opposed to TABLEUPDATE() which applies only to one work area.

>
>Rajesh