Control Applet with MetriQ Time Tracking Software

Use the control applet to manage MetriQ's connectivity to either a local database on the same machine or to a database on a remote server.

Note: If during the use of MetriQ you wish to connect to a different database, you should first disconnect MetriQ. The Database Connection button on the MetriQ's window will let you do this (see also Main Page Overview)

Figure 1. MetriQ Control Applet

Using the Control Applet - Configuration: The Control Applet is used to configure access to the RDBMS used to store all of MetriQ's data. MetriQ operates as a Client/Server and as such, there are various settings that must be set to facilitate the correct working of the MetriQ software.

Server Mode (default): Server Mode, is the default setting for MetriQ. In this mode, the RDBMS runs transparently on the same machine as the MetriQ software. You will need to specify LocalHost as the connection protocol, and indicate the location of the MetriQ database file (.fdb/.gdb) in the Database File.

Note: A server name is not required when running as LocalHost. However, should you wish, you may also use any other communications protocols, naming the Sever as the local machine.

Client Mode: When in client mode, it is understood that MetriQ has been installed with a client configuration on the target machine. In this instance there is no RDBMS running on the target machine. Use the Control Applet to ensure that you connect to the remote Server that has the RDBMS installed. In this mode, you will need to specify the connection protocol and also the name of the remote server to connect to.

Protocol: TCP/IP is the standard protocol used.

Port: Typically this value is 3050 - see your system administrator if this has changed recently.

Server: You will need to specify a server name, which will be machine running the RDBMS and the MetriQ database. Note: you can also use the dotted IP address e.g. 203.96.88.111 rather than the machine's intranet name. It's also possible to connect the client to another machine across the World Wide Web. In this instance, a third party packet encryption software should be used (eg Zepedee) or a Virtual Private Network (VPN).
If a server name is not specified, localhost (127.0.0.1) is assumed.

It should be noted that MetriQ can run remotely using VPN. That is to say that a client can open and execute software while using MetriQ on a remote server. MetriQ's Terminal Server software must be installed on the target server for this to work correctly.

Database File: Specifies the path location and file name of the MetriQ database file (.fdb/.gdb) on the Server. Note: the location of this file MUST not be in a SHARED directory.

Buttons: Additional Functionality of the Control Applet - Database Administration Tools:

	Backup Database: It is inadvisable simply to copy the MetriQ database file. Doing so when the database is in use may lead to a corrupted database file. To backup the database when in use, use the backup utility supplied. The backed up file will have an .MQF file extension (see also Database Maintenance) - more on backup below.
	Restore Database: Restore the MetriQ database from a previously backed up database copy. The restore database function requires an .MQF database file (See Backup Database above). Note: Make sure MetriQ is closed before doing a Restore (see also Database Maintenance) - see more on restore below.
	Pack: Packing is an inevitable part of database maintenance. When you delete records from a database, the space those records took up is not reclaimed until after you have done a pack. Use pack on a regular basis to keep your database in tip-top condition. It is always advisable that you do a backup of your database before issuing a pack.
	Archive: As the number of records in a database grows, the speed of access to the data diminishes. For this reason, you may wish to use the archiving utility tool (Archive Pad) that comes with MetriQ. Using the Archive Pad allows you to move or copy timing data into a new target database. When using this functionality, the following options need to be set: Year: Pick the year for which timing data is to be moved or copied to the archive database (typically the software will append _ArcYYYY at the end of the database name where YYYY is the archive year). You may choose to save your archived data either as a regular database (.fdb/.gdb) file or as a compressed backup (.mqf) file. Move Timing Data Checked: Timing data will be physically moved from your source database (the one that is currently in use) to your new destination (target) database. Once moved the data will no longer be available in your source database. Move Timing Data Un-Checked: Timing data will be copied from your source to the target. The timing data on the source will still be visible after the archiving has finished. Verbose Mode: A detailed itemised list of steps for the archive process. Send to Log File: Send archive process steps to a Log File. Archive: This begins the archiving process. Note: this process may take some time depending on the volume of data to be archived and the speed of your computer. Note: ONLY timing data is moved or copied into the named archived database file. All other database settings remain the same. In this way, you may open an archived file and see exactly the state of your timing data for the selected time period. Note: Although the archive works in units of years, should you wish, you may archive in what ever fractions of a year you wish. e.g. On March 31 2005, if you do an Archive for 2005, all data for this first quarter will be saved in a separate database file. From the 1st April, your data will only reflect timing data for the second quarter 2005, so you can repeat this step for each new Quarter.
	Test Connection: The test button allows you to test both the name of the server and the database file it is to access, either in LocalHost mode for a single user or with any of the other protocols for network connection.
	OKay: Leave the Control Applet
	Help: This Help Page

Backing up and restoring MetriQ: MetriQ has the facility to backup and restore its databases. The backup file type is .MQF and is compressed for ease of storage and transmission over the network or the World Wide Web. It is important to backup your data on a regular basis, preferably to a different machine or removable medium. This offers piece of mind should your machine's hard-drive fail or such occurrence resulting in the loss of the original database.

Backing up: When backing up a MetriQ .fdb/.gdb database file, you are first asked to supply the name of an existing source .fdb/.gdb file. Next you will be asked to supply the name of the destination back up file. You can use an existing .MQF file and have the data overwrite the current contents or enter a new file name. Details of the backup process can be seen with 'show details'.

Restore: The reverse process to backup. Now you are asked to supply the name of an existing source .MQF file and then the name of the destination .fdb/.gdb file to be restored. Again details of the backing up process can be seen in 'show details'.

Note: The list of servers and database files used by the drop down menus are simple text files located in the sub directory \MS_DF below the MetriQ install directory. The file names are Server.tvs and Databases.tvs and can be edited using a text editor such as Windows Notepad.

Database Servers: Windows Versus Linux: There are slight path differences when using a Windows machine to run the database server (Firebird or Interbase) compared to that of a Linux machine.

Windows: With Windows a full path name and drive description of the database location must be given. e.g. a typical install will give:

c:\Program Files\MetriQ\DBMQF\IBMetriQ.fdb or \IBMetriQ.gdb

This value is used as the database file name for a Windows server.

Linux: However for a linux machine, the naming convention is a little different, and would typically look like this.

/DatabaseDir/MetriQ/DBMQF/IBMetriQ.fdb or /IBMetriQ.gdb

Database Security Tab: If you are running MetriQ in conjunction with a Firebird RDBMS that has been setup with its own security, then you will need to complete the fields UserName, Password and Role. Don't forget to activate these settings by checking the 'Enable DB Security' checkbox.

Switch Databases (Menu > Tools): If you are using MetriQ in Synchronized mode, then you can use the Switch Database to switch between your Master and Portable databases. See also Synchronization.

See also Multi-User Environment, Database Security, Connection Issues,Installing MetriQ, Firewalls, System Requirements and Troubleshooting

©Copyright 2004-2007 MetriQ Limited All Rights Reserved. MetriQ Software is Patent Pending

site map