>Actually that is what I have done. Before I begin my transaction I do all the updating, then begin the transaction and if any of the updates fail I issue a rollback and then do tablerevert on all the tables. But is this an ok procedure to follow in the future. Should I have instead done my updating say on one table within the transaction, issue a tableupdate and if that failed issue a rollback before attempting to update the second table. Or is it ok to do all the updating outside the transaction and then issue rollback and table revert on all the tables.

Yes, its fine to do all the updates, then start the transaction and do all your tableupdates. That's actually the preferred method since it leaves the lock on for the shortest time.