Chapter 15
In This Chapter
Verifying data
Backing up and restoring a database
Turning on security
Tracking actions in the database
Using Station Administrator to resolve problems
After you get information into your database, you should implement some safeguards to ensure that you haven’t wasted your time. In this chapter, you learn how to
Most of the tools described in this chapter are used by those who administer the Timeslips environment.
As you work in Timeslips on a day-to-day basis, errors can creep into your Timeslips database. These errors might not be apparent immediately, but eventually they can corrupt your data to the point that the database becomes unusable. To avoid this situation, you should plan to periodically verify the validity of your database using the Data Verification feature. In many cases, if the Data Verification tool finds corruption, it can repair that corruption.
Typically, you run Data Verification once to simply examine the database for errors. If Data Verification finds no errors, you’re done. If the tool finds errors, you rerun the tool using different settings. The Data Verification process can take considerable time, depending on how much data you store in the Timeslips database. Plan to run Data Verification during an off-peak usage period, perhaps at the end of the workday.
To run the Data Verification tool, follow these steps:
Timeslips displays the Data Verification dialog box shown in Figure 15-1.
A message appears, explaining how data repair works and asking if you want to start repairing data. The message is a bit misleading because Timeslips won’t repair any errors it finds during the process of looking for errors.
Timeslips prompts you to make a backup of your database. Because the Data Verification tool won’t make any changes, you can skip the backup this time.
The Data Verification tool begins to run, and you see a progress bar. When the tool completes its analysis, the Data Verification Results window shown in Figure 15-2 appears.
At the top of the Data Verification Results window, Timeslips reports the number of errors that were found. You can scroll down in the window to review the tests that the Data Verification tool made and their results. This report can be useful to Timeslips–certified consultants or Timeslips Technical Support personnel if you need to contact them for help repairing the database.
If the Data Verification tool reports errors in your database, repeat the preceding steps, making the following changes:
The Data Verification tool will attempt to repair any data index problems in your database. If the Data Verification tool still reports errors in your database, repeat the previous steps but, in Step 2, select Look for Errors and Rebuild Data Indices.
If the Data Verification tool continues to report errors, rerun the tool, this time selecting Look for Errors, Rebuild Data Indices, and Validation Errors.
If your database errors pertain to accounts receivable balances or funds balances, you can use the settings at the bottom of the Data Verification dialog box to rebuild those balances for one or all clients.
Although the Data Verification tool will attempt to repair as many errors as it can, it cannot repair all errors. If your database is badly corrupted, the Data Verification Results report will recommend that you restore your database from a backup. Read on.
Your Timeslips database is probably the most valuable asset your company owns. After all, it stores all the time you’ve spent working and all the bills you’ve generated, both paid and unpaid. Without your Timeslips database, you might find yourself in the unenviable position of not knowing how much your clients owe you and how much to bill your clients for work you’ve performed.
You know that popular little saying, "Stuff happens.” (That’s not exactly how it goes, but you know what I mean.) Well, it’s true. Computers fail, data gets deleted or corrupted, and disasters such as fire or theft can occur.
Because the Timeslips database is actually a collection of database files, you should use the Timeslips Backup tool to make your backup. The Timeslips Backup tool ensures that you back up all the files you might ever need to recover from a disaster.
Please don’t say that your network administrator backs up your server every day. And please don’t tell me that you back up to the cloud. My answer: You still should make your own backup using the Timeslips Backup tool. My years of experience are talking here.
Why am I pushing using the Timeslips tools to back up? Because I can then guarantee that you’ll know how to restore your Timeslips database in case of an emergency. If you don’t have a backup made using Timeslips tools, you need to ensure that you know how to restore your database using some other tools. (Backups that you don’t know how to restore are hardly useful.) I think you’ll find the Timeslips tools very easy to use.
The question I’m asked most often is, “How often do I need to back up?” And my answer is always, “How much data are you willing to re-enter into Timeslips?” If you use Timeslips daily, I think you should back up daily. That way, if a disaster occurs on Day 2, you can restore the backup from Day 1 and re-enter only Day 2’s work. Plan to back up at the end of each day, before you leave work. Even large Timeslips databases typically take no more than 20 minutes to back up, and smaller databases take considerably less time — just a few minutes. While your backup runs, you can clean up your desk and get ready to go home.
You should keep more than just yesterday’s backup. I recommend that you keep 10 backups—one for each of the last 10 days. Why? Refer to the Data Verification section in this chapter; sometimes, errors creep into your database without your knowledge. If your database becomes corrupted and you have only one backup, chances are good that you’ve backed up the corruption, and that backup won’t be worth much. However, if you keep several backups, you give yourself the chance of having to re-create only a few days of work instead of losing everything. And keeping 10 backups is easy to do, as you see in a moment.
You should save your backups to a hard drive other than the one that stores the original database. You can, for example, use an external hard drive or flash drives. Both mediums are reliable, inexpensive, fast, and portable. I prefer an external hard drive because I can fit all my backups on it and know exactly where to find the latest backup.
When you create your backup, Timeslips suggests that you name the backup file Timeslips Backup. That’s insufficient. You should add today’s date to the beginning of the filename so that your backup files have names such as 10-31-13 Timeslips Backup and 11-01-13 Timeslips Backup. Using this naming convention, you can easily identify the most recent backup file, which is the one you’ll want to try first if you need to recover from a disaster.
To back up your Timeslips database using the built-in tools supplied in Timeslips, follow these steps:
Timeslips displays the Back Up Current Database dialog box, which lists the folder location of the current database, the date you last made a backup, the question, Do You Want to Make a Backup?, and the Include Subfolders Found in Your Database Folder check box.
Timeslips displays the Name the Backup File window shown in Figure 15-3.
As you can see in Figure 15-3, I store my backups in a folder called Timeslips Backups on my LaCie external hard drive.
I add today’s date to the default name that Timeslips supplies, which is Timeslips Backup.
Timeslips automatically assigns a file type of .BKU (for backup) to all Timeslips backup files. In that way, you can easily distinguish Timeslips backup files from all your other files.
A progress bar appears as Timeslips backs up your database. When Timeslips finishes backing up, a message appears, indicating that the backup was successful.
And that’s it — you’ve made a backup. Don’t forget to choose Special⇒Exclusive Mode to give others access to the database.
So, the moment arrives when disaster strikes. You knew it would; it’s Murphy’s Law — anything that can go wrong, will go wrong.
But you’re prepared. You have your Timeslips backups that you can use to recover from disaster. Picture me patting you on the back for making those backups. If I were there, I’d be cheering!
To restore a backup, follow these steps:
By default, in the Select a Backup File to Restore box at the top of the dialog box, Timeslips displays the location and filename of the last backup you made. If necessary, click the Browse button (the three dots) beside the filename to locate and select the backup that you want to restore.
If you choose the Current Database option, Timeslips restores the backup to the same folder where the original database was stored. If the original database became unusable, you have nothing to lose by overwriting it. If the original database was not unusable, you can make a copy of it before overwriting it by selecting the Back Up the Current Database First option and the Include Subfolders of the Current Database in the Backup option.
If you choose the Choose a New Location option, you can restore the backup to a new folder of your choice.
Timeslips restores the backup you selected in Step 4. If you opt to restore to the original location and back up the original database before restoring, Timeslips first makes a copy of the original database.
When Timeslips finishes restoring, a message appears, telling you that Timeslips successfully restored the backup.
Don’t forget to choose Special⇒Exclusive Mode again to give other workstations access to the database.
Now, admit it — wasn’t that easy?
Using the Timeslips Security feature, you can assign passwords to your Timeslips data so that only those who know the password can open the database. Further, you can establish exactly what any particular timekeeper can (and cannot) do while working in Timeslips.
Setting up security is a three-part process:
You turn on the Timeslips Security feature when you set up global security options and establish a supervisor password. Follow these steps:
Timeslips displays the Global Security dialog box (see Figure 15-5).
Nobody but the security administrator and the company’s owner should know this password. It is not case-sensitive; Timeslips stores the password in all uppercase letters, even if you type it using uppercase and lowercase letters.
If you want to allow someone without a password to log into your database, you can create a timekeeper named Guest, set up a profile for it, and then permit it to log in by selecting it in the Guests Log in Without a Password Using drop-down list. Be aware that third-party programs that connect to Timeslips are subject to security, and some might try to use the Guest login, so set up the guest’s profile carefully.
Timeslips displays a message telling you to write down the password you assigned and keep it in a safe place.
Another message appears, prompting you to log in.
This dialog box appears each time any user opens the database.
After you finish setting up security, timekeepers will select their own names from the list and type their own passwords.
You create security profiles to store a collection of rights you want to assign to timekeepers.
Follow these steps to create a security profile:
Timeslips prompts you for the supervisor password.
Timeslips displays the Security Profile List window. The window contains one profile — the Default profile, which provides complete access to all Timeslips functions. Typically, you reserve the Default profile for the Timeslips database administrator who uses the supervisor password to log into Timeslips.
By default, Timeslips assigns permission to all areas of Timeslips when you create a new profile; you remove check marks from the Rights list to limit permission to that area.
Timeslips displays a message explaining that security settings have changed and asks if you want to log in again to enable the new settings.
After you’ve established profiles, you need to assign each of your timekeepers to one of the profiles and establish passwords for each timekeeper.
To assign timekeepers to profiles, follow these steps:
Timeslips prompts you for the supervisor password.
Timeslips displays the Timekeeper Security window, which lists all timekeepers set up in your database.
Timeslips displays the Timekeeper Security Setting dialog box shown in Figure 15-8.
The timekeeper uses this password to log into your Timeslips database.
To make your life easier, you can initially establish the same password for each timekeeper. When you notify your timekeepers of the password, also tell them to change the password by logging in with the initial password and then choosing Special⇒Change Password.
Timeslips displays a message explaining that security settings may have changed for the current user and asking if you want to log in to see the effects of the changes.
Timeslips displays the Database Login dialog box shown previously in Figure 15-6.
Let your Timeslips users know that they can choose Special⇒Logout and Lock to log out of the database without exiting Timeslips. By using this command, your Timeslips users can walk away from their desks knowing that the Timeslips database is secure.
If you enable Timeslips security and require that each timekeeper use a password to log into the database, you also can use the Audit Trail feature to track who takes actions in your Timeslips database, what actions are taken, and when they happen. After you enable audit trail tracking, you can control how much data the feature tracks and you can print the Audit Trail report to review the actions taken in your database.
To set up the Audit Trails feature to track information in your database, follow these steps:
The Audit Trails Setup dialog box shown in Figure 15-9 appears.
If you don’t see the Audit Trails command, choose Setup⇒Features Enabled and make sure that a check mark appears next to the Audit Trails option.
For security, you should make this password different from the security supervisor password, but make sure that your company’s owner and the security supervisor know this password. It is not case-sensitive; Timeslips stores the password in all uppercase letters, even if you type it using uppercase and lowercase letters.
A table is a collection of records in a database, and you can enable the Audit Trails feature for specific tables in your Timeslips database. By default, the feature tracks all changes in all database tables.
To track only certain data in the database, open the Tables drop-down list and select the table. Then
Timeslips displays a message identifying the Audit Trails feature password.
Timeslips prompts you to add initial audit trail data for records in the database that already existed when you enabled audit trails.
Timeslips updates audit trail data.
To view audit trail information, choose Special⇒Audit Trails to display the Audit Trails window shown in Figure 15-10.
Use the options at the top of the window to limit the audit trail data shown in the middle of the window, and click an entry in the middle of the window to see the audit trail data for that entry in the bottom of the window. You can print the information by clicking the Print (printer) button on the vertical toolbar. You can print the report also by choosing Reports⇒Other.
The Audit Trail feature can generate a lot of data. Periodically, consider purging audit trail data by clicking the Purge (X) button on the vertical toolbar in the Audit Trails window. Timeslips displays the Purge Audit Trails dialog box, where you can select audit trail records to purge. You also can print a report of the audit trail data that you purge.
Station Administrator is a tool for Timeslips database administrators to help resolve some issues that might arise. The Station Administrator window lists all workstations currently accessing the Timeslips database and displays the location of the current Timeslips database. To use Station Administrator, close Timeslips and then, from the Timeslips group on the All Programs menu, choose Station Administrator. The window shown in Figure 15-11 appears.
The Timeslips database administrator can use Station Administrator to solve a number of problems. For example, if you see the BDE settings are too low error message when you open your Timeslips database, you can choose Options⇒Diagnose This Computer to solve the problem. Station Administrator displays the Diagnose This Computer dialog box, which contains four Fix buttons. If any of them are available, click them to fix the associated problem.
The list of all workstations accessing the current database should refresh as workstations open and close the database. However, if you need to reboot a particular workstation while that workstation has Timeslips open, the list might not update properly. You can click the workstation in the Station Administrator window and then click the Clear button.
By choosing Options⇒Licenses In Use, you can identify the number of Timeslips licenses you own.
If you see the Another program is accessing your Sage Timeslips database error message, you can choose Options⇒Change Install Path to select the correct Timeslips configuration file.
You also can choose Options⇒Change Timeout Settings to automatically log out workstations logged in-to the Timeslips database when these workstations have been inactive for a period of time you specify. This feature is particularly useful if you back up Timeslips in the middle of the night and one Timeslips user accidentally left Timeslips running at the end of the day.
3.138.101.69