Keep in mind the following before renumbering transaction codes:

Archive Transactions - The transaction code numbers will be renumbered in the archive files as well. If your archive files are large, allow additional time for the renumber process.
Renumber Multiple Tcodes - It is much faster to renumber several transaction codes at one time than it is to renumber each one separately.
Activity & Expense Codes - Each Activity code and Expense code is assigned a transaction code in the Task Code window. If one of these transaction codes is renumbered, it will change the transaction code assignment in the Task Code window.
Cost Rate Table - Renumbering a tcode renumbers the tcode specified in a Cost Rate Table.
PracticeMaster - Renumbering a tcode in Tabs3 Billing renumbers the tcode in PracticeMaster.
TAS - Depending on which transaction codes are being renumbered, you may need to change the transaction codes specified for each bank account in Trust once you renumber the Tabs3 Billing transaction codes.
Tabs3 Remote - If you use Tabs3 Billing Remote, you must merge all transactions from the remote workstation(s) before renumbering. After renumbering, be sure to recreate the remote validation files and transfer them to the remote workstation(s).

Data Capture Device - If you are using a data capture device, you must merge all transactions from the device before renumbering.

Depending on which transaction codes are being renumbered, if you are using a data capture device, you may need to use the interface program to assign a new default transaction code before using the Merge Data Capture Transactions utility.
GLS Accounts Table - The Renumber Tcode utility also renumbers a tcode specified in a GLS Accounts table.