How To
- Approve order function.
- Cost Activities
- How does the “Approved Supplier” (QA status) functions work?
- How does the Approve direct purchases onshore work?
- How does the rule-based approval matrix work?
- How To - Set Failure Report Running Number
- How To - Add SQL Server to Windows Firewall Exception
- How To - Access the report template editor
- How To - Accounts and Budget (v. 2.662 and later)
- How To - Active a unit for use with the Incidents Module
- How To - Add same document on multiple components
- How To - Approve Purchase Orders and Change Requests when using Approval Rules and Change Approval
- How To - Assign user rights
- How To - Automatically resize images
- How To - Backup TMv2
- How To - Cancel Job History (Job Signed Out In Error)
- How To - Cancel job history (Video Link)
- How To - Catalogs
- How To - Change a Unit Code in TM Master V2
- How To - Check for File Not Found Error. Document Handling.
- How To - Circulating Components
- How To - Company tags
- How To - Connect the TM Master v2 Client Application
- How To - Connect the TM Master v2 client to more than one database
- How To - Contract Management
- How To - Copy Components, Component Jobs and Spare Parts
- How To - Create a new unit
- How To - Create a New User TM Master v2
- How To - Create and use batch jobs in TM
- How To - Create Credit Note
How To - Find and understand the TM Master v2 version number, and how to identify the database version
How to find the TM Master v2 client version number
The full TM Master v2 client version number can be found under [Help -> About]:
For administrators: How to find the TM Master v2 service version number
The TM Master v2 service version number can be found in the service log at the start of each service loop:
How to understand the version number and identify the database version
A typical TM Master V2 version number looks like this:
2.662.7636.16913
If we break it down, the different number sequences have the following significance:
2.662.7636.16913
This is the main version number (hence TM Master V2). If the main version of two installations differ, then their databases are not compatible. To upgrade requires a manual conversion of the database. Please contact us for more details if you are interested in having this done.
2.662.7636.16913
This is the database version number. To upgrade from one database version to another (for example from 660 to 662), an automated upgrade of the database is required.
Different database versions are not forward compatible for replication, so it is not possible to replicate data between an office and a vessel that have different database version numbers. This means that to perform a successful database upgrade, the entire fleet needs to be upgraded in one operation.
The TM Client and TM Service are not compatible with different database versions. This means that all TM Clients and TM Services must be the same database version as the database they connect to in order to function.
2.662.7636.16913
This is the hotfix version number (also known as the patch version number) which does not generally affect the structure of the database. To upgrade from one hotfix version to another does not require a database upgrade.
Different hotfix versions are compatible for replication, so it is possible to replicate data between an office and a vessel that has different hotfix versions as long as the main and database version numbers are the same.
The TM Client and TM Service are compatible with different hotfix versions, so as long as the main and database versions are the same any combination of hotfix versions will generally be able to connect to and work with the database.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article