ClockedIn 2 - Send Database

You can send a copy of your ClockedIn 2 database in an e-mail using the "Send Database" feature. This feature is set in ClockedIn 2 settings acceseed through the iOS Settings app. Here's how to set your iPhone/iPod touch to send its database:

  1. Launch the iOS Settings app.
  2. At the Settings app's main screen, scroll down to the ClockedIn 2 icon and tap on it to access ClockedIn 2's settings.
  3. Scroll down to the "Data" section in ClockedIn 2's settings and tap on "Database". This will present the "Send Database" screen.
  4. Now, slide the switch to "ON'.

When set to "ON", the next time ClockedIn 2 is launched, it will create an email with a database archive file attached to it. You can now send the e-mail and its attachement to yourself for safe keeping.

Loading a Database Archive.

You can load a database archive into ClockedIn 2 by tapping on the database archive file in an e-mail. This will launch ClockedIn 2 and allow you to load that database into the instance of ClockedIn 2 running on that device.

It's important to note, that the current ClockedIn 2 database will be replaced by the database in the archive. All data in the current database will be deleted.

Frequently Asked Questions

  1. Are application settings contained in the database?

    No. Appliation settings are not stored in your ClockedIn 2 data. The database stores, timed tasks, projects, project activities, and customers.

    Properties configured through the Settings app are not contained in the ClockedIn 2 database.

  2. Is the database archive compatiable between ClockedIn 2 and ClockedIn 2 for iPad?

    Yes. The database archives produced by both products is identical in format. You can load a database archive that was created on ClockedIn 2 into ClockedIn 2 for iPad and vice versa.

  3. Can I use this feature to keep my ClockedIn 2 and ClockedIn 2 for iPad in sync?

    Maybe. While we don't consider this sync, it can provide those that are running ClockedIn on multiple devices help in managing their data across those devices. There are situation where this may work fine for syncing ClockedIn 2 across your devices. However, there are some issues you need to be aware of:

    • Customers assigned in ClockedIn 2 using your iOS address book will likely break.

      The unique ID that identifies contacts in your address book are designed to be unique, even across devices you own. That means that the association of a contact in your address book to a customer in ClockedIn 2 on one device will not be the same on another device.

      The workaround is to not use the "Select from Contacts" option when assigning customer names and enter the names manually.

    • Data loss.

      The database on one device is being replaced by the other device's database.

      It's easy to create a situation where each device has unique data and replacing either of the databases with the other's database will cause the unique data on the device to be lost. For example, device 1 has A and B. Device 2 has A and C. If you replace device 2 with device 1's data you will lose C.

      One way to avoid this is to use one device as a "master" and the other as a "slave". Whie the roll of master device and slave device can switch between devices, you'll need to know which is which when loading database archives.