How to Restore Sage Timeslips Archives - dummies

How to Restore Sage Timeslips Archives

By Elaine Marmel

To use slips you placed in an archive file, you need to import them into a regular Sage Timeslips database. Although nothing stops you from importing them into your regular Timeslips database, that process can turn messy in a hurry.

If you import the archive slips into your regular Timeslips database, you’ll need to purge them again when you finish using the archived slips. And when you do that, you need to make sure that you set up your filters to remove only the archived slips — a potentially messy situation.

Creating a separate database in which you store the purged slips is much safer. That way, they don’t go back into your regular database and mix with your active data.

If you want to use the archived slips in a database on a different network than your regular database, copy the archive file to that network. Remember, though, that you need access to the Sage Timeslips program to use the archive file.

The first step to take is to create a new database. For this example, you can create a database based on the original database you use every day, and place it in a folder called Data02 Purge.

When you base a new database on another database, Timeslips automatically populates the new database with the nicknames in the original database along with the details for those nicknames. You can accept most of the defaults the wizard suggests as you create the database. You might want to deselect the Synchronize Data with MS Outlook option, but the other defaults work fine.

If you use more than one Timeslips database, you might want to include the database name, along with the word Purge, when you name the database folder.

After you create the new database, Timeslips opens it. Check the bottom of the Timeslips window beside the Guides button to confirm that you’re using the Purge database you just created. To combine the archived slips into the Purge database, follow these steps:

  1. Choose File→Combine to display the Sage Timeslips Import window.


  2. Confirm that the Put Data Into option is set to Default.

    The default database is the one you’re currently using, the Purge database.

  3. Click the Browse button (three dots) beside the Get Data From option.

  4. Navigate to the archive file you created.

  5. Select the archive file and click Open.

    In the example, the archive file 11-30-13 Data 02 Archive.SAR was selected. The Sage Timeslips Import window reappears, displaying the archive file containing the slips you want to import in the Get Data From box.

  6. Click the Import button.

  7. When Timeslips prompts you to back up the Purge database, do so.

    It can’t hurt to have a backup.

    After the backup process finishes, Timeslips begins to combine the slips into your empty Purge database. Because the database is empty, Timeslips doesn’t recognize any of the nicknames on the slips, so a dialog box appears.

    You see the Nickname dialog box only when a nickname on an archived slip doesn’t exist in the Purge database.


  8. Click the Add All button.

    Timeslips adds all client nicknames.

  9. Repeat Step 8 for tasks, expenses, and timekeepers if Timeslips prompts you.

When the import process finishes, Timeslips displays a dialog box that summarizes the number of slips it imported.

When you click the X in the upper-right corner of the Sage Timeslips Import window, you are prompted to save the settings in the window. It is suggested that you plan to create separate archive files each time you purge slips; in this case, you don’t want to save these settings, so click No.

The slips you imported appear in the Time and Expense Slip List window, and you can produce any of the slip-based reports. If you open any of the windows available in the Names window, you’ll find nicknames without any details defined for them.

Remember that you’ve imported slips into the Purge database that no longer exist in your regular Timeslips database. If you need to produce a report that includes slips from both databases, use the Exchange feature.