System crashes can be causes by power failure, hardware and network
problems, memory conflicts between programs, and other things. Several
things can happen when the system crashes while you're running TMS that
may affect the integrity of your TMS database.
The most common problem associated with a system failure if that your
user name will not be cleared from the User Log,
preventing you from being able to login to TMS the next time. Another
problem that can occur is corruption of a data table header. This results
in an error of "Not a Table/DBF." Another possible
problem is corruption of the relational integrity between two or more TMS
data tables.
You can correct the first two problems by running the DataChk.exe
utility, provided with your TMS program. Relational integrity problems
will be identified by this program, but you may need to contact us to
arrange for correction of relational integrity issues.
When you log into TMS, your user name is placed in an internal table
called the "User Log". As you move about within the program, you progress
is updated in the User Log. When you exit the program normally your entry
in the User Log is deleted.
If the program does not end normally your user name will remain in the
User Log. For security reasons, TMS is designed to not allow the same user
name to be used by more than once.
To clear the User Log, you will need to run the DataChk.exe utility,
provided with your TMS program.
A detailed white paper on this topic is available on the Client
Downloads page.
Congratulations! Moving TMS to a new PC simple.
For a Single User installation, it involves moving the existing TMS
files from the old PC to the new one and pointing TMS to the data
directory the first time you run it.
For a Network installation, it is simply a matter of mapping to the
network folder containing TMS, then pointing TMS to the data directory the
first time you run it.
A detailed white paper on this topic is available on the Client
Downloads page.
TMS has always been able to deal with training requirements like the
California POST "Perishable Skills Training" mandates. These are simply
Standard Training Requirements that are added to your TMS Training Plan.
A detailed white paper on this topic is available on the Client
Downloads page.
This error is caused by corruption of the header of one of your TMS
data tables. Fortunately, you can fix this easily by running the
DataChk.exe utility, provided with your TMS program.
A detailed white paper on this topic is available on the Client
Downloads page.
The TMS Software Support Subscription is your one-stop solution to
maximum production with your TMS program. It provides:
